Tealium migration iOS Library 4.1.11 to 5.0.1

[ivanmoya]

We have migrated to version 5.0.1, we have seen that before (version 4.1.11) the VIEW and LINKS events sent to the parameter "EVENT_NAME".

Now "VIEW" event sent to "SCREEN_TITLE" and "LINK" event sent to "LINK_ID".

You know the reason for this change? and if there any solution?

I may be wrong.

Thanks!

[jason_koo]

Hello @ivanmoya. View events were alwasy sent to screen_title and links to link_id.  Event_name was originally added as a central convenience data source.  It being redundant however, we have removed it from 5.x.  An extension could be added in TIQ to route both those values into the one event_name if desired.

[ivanmoya]

Hi Jason/kathleen,

I'm trying removing EVENT_NAME, but I see 1 and 2 HIT to XITI does not work, only works from 3 HIT forward.

The first two events are not sent to XITI HIT, the following events I think they are working properly

In the following example have 3 HITS: 1. Splash, 2. Home. and 3. Menu. The problem we have detected is that the first 2 events do not generate the HIT to XITI, in the following example only see the HIT to XITI generated for the event Menu.

Maybe the problem solved with version: 5.0.2 ? I test now with version 5.0.2 and not work.

• TealiumIOSLifecycle.framework and sample app added to Support folder
• Initial queue size init after first launch for default -1 setting fixed
• CaptureTimeDataSources now safely adds additional data for certain launch edge cases
• DestroyInstanceForKey: method now properly clears persistent data
• Additional Data Source Keys to support lifecycle module added
• Offline TagBridge feature enabled

Best Regards

Ivan

[jason_koo]

Hey @ivanmoya,

Do you have any screengrabs of where in your code the track calls for the Splash and Home views are being triggered?  I'm curious to know which methods they are in.

[ivanmoya]

Hi @jason_koo. The code is the same for all tags, and for example the Tag "Home" works properly after those first 2 tags that do not work.

I do not understand, it seems a problem in the configuration profile Tealium or APP code.

I'm talking to support, I hope something happens to them. We put back to version 4.1.11 that if it worked.

I would like to know what is the reason for the jump uconnect.tealiumiq.com HIT. According the photo, only the first 2 firts Tags only HITS datacloud.tealiumiq.com chips, but not the uconnect.tealiumiq.com 

According to the photo, the first 2 HITS only see the datacloud.tealiumiq.com, but not the uconnect.tealiumiq.com, but 3 HIT tag if you see the uconnect.tealiumiq.com.

Thanks you

Iván

[jason_koo]

Hi @ivanmoya,

Support through your Tealium account manager is the best option at this point, as they will have access to your account to verify everything in TIQ is set up as desired.

Version 5.x has the ability to send background collect calls to our audience stream system (Collect Dispatch Service) and/or via the Collect tag from TIQ (Tag Managment Dispatch Service).  The desparity in calls you're seeing may be cause by a difference in configuration between these 2 options.  Again, your account manager will be able to review your TIQ settings to check.

Additionally, I was unable to view the screengrabs you had posted earlier. Perhaps try a different image format?

[kathleen_jo]

Hello @ivanmoya. I believe your account manager is @dburgess. He should follow up with you shortly. Thank you!

[ivanmoya]

Hi @kathleen_jo, thanks for answer.

We are talking with @simon_taylor, but we still have the problem.

@dburgess I do not know, could you contact us?

Next week we believe publish to Production enviroment, and we have a decision about this, implementing with v.4.1.11 or v.5.0.2.

Thanks!

[dburgess]

Hi @ivanmoya absolutely I will have your account manager @Anonymous reach out to you.