Data sources send data into Tealium. A data source can a website, a CRM system, a mobile SDK, a server-side application, or even a webhook. The number of possible data sources is endless, however there are two primary methods for sending data to Tealium: web-based and API-based. Choose the method that matches your platform to determine how you will send data to Tealium.
A successful CMS integration loads the Universal Tag and dynamically populates a data layer with built-in system data, such as page name, site language, and user login status to name a few. An e-commerce platform would populate product and order variables on the relevant pages in the system.
API based integrations use the Tealium Collect HTTP endpoint or a custom endpoint to send data to the Tealium Customer Data Hub. This approach is useful if your system supports triggered callbacks or webhooks. The most common platforms for API integrations are CRM and email marketing platforms.
The following lists the available API data sources integrations:
Tealium users can easily onboard and unify data from various systems to create personalized customer experiences.
Tealium users can identify the origin of all incoming data for a clearer understanding of their data supply chain.
Higher quality of incoming data.
Tealium offers a file import data source which processes CSV files from several cloud storage providers. However, file imports are not currently offered as an integration method for partners.
Mailchimp is an all-in-one marketing platform that offers webhooks for common email actions such as subscriptions, profile updates, email changes, and campaign statuses. For example, when MailChimp receives a subscribe action it can trigger a webhook with the data related to that event. In this case, the subscribe event type has the following fields (brackets indicate nested JSON):
Tealium’s official data source integration with Mailchimp offers these additional benefits from using the generic HTTP API:
Tealium issues a customized endpoint for this data source. For example: https://collect.tealiumiq.com/integration/event/my_account/main/abc123.
Tealium flattens the JSON body and prepends mailchimp_ to all field names to give all MailChimp data its own namespace. For example, "data[merges][EMAIL]" becomes mailchimp_data_merges_email.
These benefits provide improved data quality and governance for all downstream data enrichments and actions. By combining the MailChimp data source with other data sources and activations, Tealium users maintain a more accurate and up-to-date single view of their customers.