This value defines the cache Time to Live (TTL) for your Infusionsoft data in the Memberium database in seconds. Contact caching was one of the original features that Memberium was designed to support since version 0.1.
The default value is 0, which means no caching, the contact records will be refreshed on each and every login.
To cache the data for one hour, you would set the Cache Age to 3600. To cache the data for one day, you would set the Cache Age to 86400.
There is no upper limit on the amount of time you can cache the contacts for. The lower limit is 0.
What is Caching?
Infusionsoft data is expensive to retrieve because of the relatively long time it takes to send the request to the Infusionsoft server, and then retrieve the results.
Caching is used to store this data in the local database for a limited time, for later reuse, so that it does not have to be retrieved every time it’s needed. This can reduce the load on your API, increase the speed of API heavy actions such as logging in, and improve your user’s experience, and make your site more resilient to any outages in Infusionsoft’s API.
Memberium allows you to define how long your Infusionsoft data will be locally stored and used before refreshing it from Infusionsoft’s servers.
Why do I want this?
Memberium employs algorithms to cache your Infusionsoft data locally for faster access. Retrieving data in realtime at login from Infusionsoft not only consumes your API calls, but is hundreds of times slower than retrieving the data locally. A typical Infusionsoft API call requires approximately 1/2 second in order to return a single response, assuming that the API succeeds on the first attempt. By using caching, your system performs faster, can handle more users, uses less API, and can make your system more scalable and reliable by decreasing the constant dependency on the API
Keeping the Cache Updated
By definition the contact caching system uses older, local data and not the most recent data from Infusionsoft. This can present a problem if you’re updating the tags or information in Infusionsoft and a client logs in and uses the older cached information.
To update the Memberium Cache with new data, you should use the update-contact HTTP POST function to notify Memberium that there is an update to the contact. The best way to do this is to add the HTTP POST in your Campaign Builder Sequence after you have finished applying and removing tags or other changes to the contact record.
Do not turn on contact caching without placing update-contact HTTP POSTs in your automation sequences to keep Memberium updated.
If you are using legacy actionsets, such as for billing triggers, you can make the update-contact HTTP POST one of the last actions in the set. To make it the last item, you need to add it last.
Use Legacy Actionsets to run your HTTP POSTs to further minimize API calls.
Questions?
Interested in taking your site performance and scalability to the next level? Have questions about implementing this? Contact us at Support
