Instructions on getting started with the Registrix service.
support related to the lead capture method of Registrix. Lead Capture is about having attendees enter data about themselves prior to being to watch a live stream event
This mode involves knowing who the attendees are in advance of the live streaming event. Methods include using a paywall service, uploading employee id or employee names
This category will involve details about 3rd party technical services that you may need to use with Registrix
In our roadmap of the Registrix application, you can discover what new services that we are working on, as well as provide feedback as to what is most important to you.
Information about how to get data and fields regarding the video streaming providers that Registrix has worked with
Third party platforms are extremely important to the Registrix Platform. Using third party platforms allows you to use the best in class for the services that they provide
There are 34 FAQs online
Behind the scenes there are a lot of new updates that you basically are not seeing, and it is about growth and performance.
As the Registrix platform has seen growth of over 1000% year over year, we have increased our usage of what is called Cache. Cache is a temporary holding place for data so that software doesn't have to go all the way back to the source to get this commonly used data. Using cache makes an application run faster, serves more attendees and makes a more stable system, but...... and theres always a but...
If you make an update in the management backend, the viewers may not see it right away because of cache. Registrix is now using two levels of caching. There is a level of cache between the website and the database server of which you can clear. The Admin can perform by clicking on the Profile menu and selecting Flush Cache. This will then flush all the cache used in between the database server.
We have another layer of cache at the attendees login page specifically. Now this cache you cannot clear. This level of cache will exists for 5 minutes and is created after 10 hits to the login page. There is no way for use to clear this cache because we don't know what server the cache exists. This level of cache is created after 10 different requests, the webserver will build a cache and serve up this login page to as many viewers making the request.
So if you are testing out your login page, and then make changes, you may need to wait 5 minutes until that cache is auto purged, and then you can see your updates.2021-05-04 18:15
A api button cname custom data data fields definitions dimensions dns domain domain name enrollment event types eventbrite excel Field getting started godaddy integration livestream login page login screen logo nameservers ns participants paywall paywalls playlist videoid registration shopify ssl sync templates TLD universe upload upload logo Video ID vimeo watch page zoom