Passing on Member ID to Web-based Services
When integrating third-party systems with our mobile app, passing customer-specific data ensures a seamless user experience. This eliminates the need for members to re-enter their details while interacting with external services. Here’s how you can achieve this with dynamic links and our APIs.
Creating Dynamic Links
To pass customer-specific data, use dynamic parameters embedded in the third-party service URL. For example:
https://example.thirdparty.com/?uuid={{member.id}}&source=trifft_mobile
- uuid={{member.id}}: Dynamically includes the unique identifier for the user.
- source=trifft_mobile: Specifies the origin of the request for tracking or analytics purposes. This is optional but helpful for reporting.
To understand more about how UTM parameters work and their use in tracking data, refer to the Wikipedia page on UTM parameters.
By embedding such parameters, the third-party system receives the required data directly in the link.
Fetching Customer Details
Once the third-party system receives the link, it can extract the uuid parameter and use it to fetch details about the user from our API. For instance, you can use the Get a Member Detail API to retrieve the customer’s information.
Make sure to authenticate your API calls with an API key. For instructions on setting up and managing API keys, refer to our API Key Documentation.
Example Workflow
- The user accesses the third-party service through a dynamic link in your app.
- The link includes the user’s unique identifier (uuid).
- The third-party system extracts the identifier and calls the TRIFFT API to retrieve customer data.
- The system uses the customer details to personalize the experience or complete an action.
Updated about 1 month ago