Understanding and utilizing URL attributes in Fin Messenger can help you effectively capture and manage data about conversation origins. This article provides guidance on how to retrieve chat start URLs, updates to the current page URL, and troubleshooting tips.
Why URL attributes matter
URL attributes in Fin Messenger play a critical role in identifying where conversations originate and tracking user journey details. For example:
The chat start URL helps determine the specific page where a conversation began.
The current page URL offers insight into user navigation and attributes important for audience targeting.
Retrieving the chat start URL
To capture the chat start URL within Fin Messenger conversations, you can retrieve it using the Conversations API. Here are the key steps:
Check the Source Field: The 'source' field in the Conversations API reveals the exact URL where a chat started. Ensure your setup is configured to query and store this field correctly.
Avoid Relying on the Referer Field: Note that the referer data often reflects the previous page, not the page where the chat was initiated.
Coordinate with Your Engineering Team: Ensure attributes like 'conversation_url' or 'conversation_source' are populated correctly at chat initiation.
Current Page URL updates
Default behavior
The current page URL in Fin Messenger is a standard attribute that updates dynamically as users navigate. It is primarily used for audience targeting in your Fin workflow but does not appear as a conversation attribute by default.
Forcing updates
Single-page applications may not trigger URL updates unless specifically set up to do so. In situations where the URL update needs to be manually triggered (e.g., in single-page apps):
Use the JavaScript method
Intercom('update', { last_request_at: Math.floor(Date.now()/1000) }).This approach forces Fin to refresh its conversation data in real-time.
Special considerations for users and leads
The current page URL updates automatically for both users and leads as they navigate between pages.
In single-page applications, ensure appropriate triggers are in place to capture navigation events.
Troubleshooting tips
If you encounter issues with URL attributes:
Confirm that your implementation is correctly storing the 'source' field for chat start URLs.
Check whether you are relying on the current page URL for purposes it cannot fulfill (e.g., conversation attributes).
For single-page applications, verify that JavaScript update triggers are properly configured.
By understanding how Fin Messenger handles URL attributes and using the provided methods to retrieve, update, or troubleshoot them, you can ensure accurate data capture and operational effectiveness. For advanced setups, like custom attributes ('conversation_url' or 'conversation_source'), consult your engineering team to align your configurations with specific data needs.