Hi everyone!
I’ve been working in an integration to show CTAs created via Hubspot to specific users based on their login email in our platform. We understood that this is done by using the tracking code API, as described in the doc Accounts Dashboard | HubSpot
Right now, when the user is logged in, the code takes their email and do the process of identification, just as explained in the doc. This works fine, however the CTA takes some minutes to start showing up (even with the CTA configured to show after only a few seconds in the page). After the first time shown, the CTA shows normally, as configured in the Hubspot platform.
Even though this is not a blocker for us, it would still be a nicer experience to receive the CTA right after the login. Because of that, I would like to know if this delay could be due to something we might be doing wrong in the integration. Or is this delay expected in the Hubspot API, perharps due to caching or something similar?
@titosilva_trink wrote:
Hi everyone!
I’ve been working in an integration to show CTAs created via Hubspot to specific users based on their login email in our platform. We understood that this is done by using the tracking code API, as described in the doc Accounts Dashboard | HubSpot
Right now, when the user is logged in, the code takes their email and do the process of identification, just as explained in the doc. This works fine, however the CTA takes some minutes to start showing up (even with the CTA configured to show after only a few seconds in the page). After the first time shown, the CTA shows normally, as configured in the Hubspot platform.
Even though this is not a blocker for us, it would still be a nicer experience to receive the CTA right after the login. Because of that, I would like to know if this delay could be due to something we might be doing wrong in the integration. Or is this delay expected in the Hubspot API, perharps due to caching or something similar?
The delay in displaying CTAs (Call-to-Actions) after a user logs in could be attributed to various factors, including network latency, HubSpot API response times, caching mechanisms, and client-side processing. Network latency between your platform and HubSpot’s servers might result in delays in data transmission, impacting the time it takes for the CTAs to be fetched and displayed. Additionally, variable response times from the HubSpot API, potential caching of CTAs on HubSpot’s servers, and client-side processing requirements could contribute to the delay. To improve the user experience and minimize delays, optimizing network connectivity, monitoring API request/response times, adjusting caching settings, and optimizing client-side processing are essential steps.
Thank you very much, @HMir! We’ve also been seeing some other strange behaviour lately.
During a test last week, we used the anonymous tab and tried to log in to the plataform multiple times, always using a new tab to ensure we would be using new cookies. In this test, we oberved that, while the identification was always sent to Hubspot servers, the CTA would not always show up. Using a single e-mail in the same environment, we saw the CTA start by not showing, then start showing after some retries, and then stop showing again, without any changes in settings of the tracking code.
Could this type of behaviour have the same cause as the previously mentioned delays?