Third Party Index

Tealium

tealium.com

Subprocessors

3 third parties, 5 affiliates. CSVof Tealium's subprocessors · Atom

NamePurposeLocationListed since
Amazon Web Services (AWS) AWS’s web application firewall (WAF), to assist in protecting web applications from malicious attacks like SQL injection and cross-site scripting (XSS), ensuring robust security and continuous availability.; Cloud hosting and infrastructure provider used to process Customer Data.As instructed by Customer during deployment of services.; Customer User Data hosted in the United States. Web Application user interface console is hosted in the US (Standard Contractual Clauses)
Databricks Processing Customer Data for analytics, data management, and AI capabilities. All Services using Databricks for AI capabilities are managed through feature opt-ins (either via a product purchase or through the use of controls in the Services), where Customer can choose which AI features it wishes to enable.As specified by Customer during deployment of Services. (Standard Contractual Clauses)
Workato Data Connect: SaaS to SaaS integration between Tealium’s CDP and Customer’s use of Workato for the Data Connect Services.As specified by Customer during deployment of Services. (Standard Contractual Clauses)
Tealium affiliates (5)
NamePurposeLocationListed since
Tealium GmbH Customer Success, Corporate Sales; Customer Success, Development, Operations, Corporate Sales; Customer Success, SalesGermany; Singapore; United Kingdom
Tealium Australia Pty. Ltd. Customer Success, SalesAustralia
Tealium Hong Kong Limited SalesHong Kong
Tealium Japan K.K Customer Success, SalesJapan
Tealium Poland S.o.o. Development, OperationsPoland

Compliance

Certified

Certifications as Tealium's trust center lists them; reports are usually shared on request (evidence)

Service status

Jul 4: before our history of this status pageJul 5: before our history of this status pageJul 6: before our history of this status pageJul 7: before our history of this status pageJul 8: before our history of this status pageJul 9: before our history of this status pageJul 10: before our history of this status pageJul 11: before our history of this status pageJul 12: before our history of this status pageJul 13: before our history of this status pageJul 14: before our history of this status pageJul 15: before our history of this status pageJul 16: before our history of this status pageJul 17: before our history of this status pageJul 18: before our history of this status pageJul 19: before our history of this status pageJul 20: before our history of this status pageJul 21: before our history of this status pageJul 22: before our history of this status pageJul 23: before our history of this status pageJul 24: before our history of this status pageJul 25: before our history of this status pageJul 26: before our history of this status pageJul 27: before our history of this status pageJul 28: before our history of this status pageJul 29: before our history of this status pageJul 30: before our history of this status pageJul 31: before our history of this status pageAug 1: before our history of this status pageAug 2: before our history of this status pageAug 3: before our history of this status pageAug 4: before our history of this status pageAug 5: before our history of this status pageAug 6: before our history of this status pageAug 7: before our history of this status pageAug 8: before our history of this status pageAug 9: before our history of this status pageAug 10: before our history of this status pageAug 11: before our history of this status pageAug 12: before our history of this status pageAug 13: before our history of this status pageAug 14: before our history of this status pageAug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: 1 incident (1 no impact stated)Sep 11: no incident reportedSep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: 1 incident (1 no impact stated)Sep 17: no incident reportedSep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: 1 incident (1 no impact stated)Sep 23: no incident reportedSep 24: no incident reportedSep 25: 1 incident (1 no impact stated)Sep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reportedSep 29: 1 incident (1 no impact stated)Sep 30: no incident reportedOct 1: 1 incident (1 no impact stated)

90 days agotoday

  • 6 incidents in 21 days
  • 0 major or critical
  • 15 h 29 min typical time to resolve
BeganIncidentImpactLasted
Apply button on custom value mapping in tagsno impact statedongoing
Delayed Connector Processing in AP-Southeastno impact stated4 h 21 min
Delayed processing on connectors in US West regionno impact stated3 days
Advanced Javascript GitHub syncno impact stated15 h 29 min
Event Feed activity graph displayno impact stated2 days
my.tealiumiq.com login and profile loading issueno impact stated8 min

Incidents per month

0 3 6 Aug 2026: 0 incidents · before our history of this status page Sep 2026: 5 incidents (5 no impact stated) · partial: our history begins Sep 10 · typical time to resolve 15 h 29 min Oct 2026: 1 incident (1 no impact stated) Aug 2026Sep Oct

critical major minor no impact stated before or partly before our history

As Tealium's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Changes

None since tracking began.

Rating badge for Tealium's site

Tealium transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/tealium"><img src="https://thirdpartyindex.com/badge/tealium.svg" alt="Tealium transparency rating on Third Party Index" height="20"></a>
[![Tealium transparency rating on Third Party Index](https://thirdpartyindex.com/badge/tealium.svg)](https://thirdpartyindex.com/vendors/tealium)