Tealium IOS behind proxy, tags don't leave

popof
Rookie Contributor
popof

Hello, we use the Tealium Framework for our IOS and Android applications, to track the activity of our customers. However, before moving our application into "production", we have a recipe phase, which is done on a network with proxy. The tags are sent very well on 4G, while those sent on the network with the proxy, do not leave. I specify that we have added an exeption for url "tags.tiqcdn.com", which is the url we see leaving. There would be other urls, or protocol (icmp, udp, other) to allow? if yes, can you tell me which one to add.

Thanks in advance.

Cordially.

2 REPLIES 2

Tealium IOS behind proxy, tags don't leave

Tealium Employee
Hi @popof. It sounds like you may be experiencing issues due to SSL pinning in your app, which will cause the app to reject all connections that don't have a valid SSL certificate (e.g. a self-signed certificate from your proxy server).

If this is the case, you will need to add exceptions for the custom SSL certificate in your app's Info.plist file in the Xcode project.

All communication in the Tealium SDKs is performed over HTTP, so you don't need to add any additional protocols. However, if you are using Tealium iQ, all your tags will be sent client-side, meaning you would need to add a proxy exception for each of the domains used by your tag vendors (e.g. google-analytics.com, facebook.com etc.).

I hope that makes sense.

Craig.
Check out our new Swift integration library for iOS, macOS, tvOS and watchOS: https://github.com/Tealium/tealium-swift with updated
documentation https://community.tealiumiq.com/t5/Swift/tkb-p/swift.

Tealium IOS behind proxy, tags don't leave

QuentinB
Bronze Contributor
Bronze Contributor QuentinB

Hi @craig_rouse 

I'm currently working with @popof on finding a resolution to his issue. 

The mobile implementation he is refering to is not using the "Tag Management" approach but is leveraging the Tealium Collect API.

From my understanding, the request that's ultimately made by Tealium to send data to EventStream is starting with https://collect.tealiumiq.com/. Would you say that adding this domain as an exception would solve the issue? Or does this type of implementation require additional configuration (for the proxy not to block eventstream data collection)?

Thanks in advance

Cheers

Quentin