Server to Server considerations?

[koen_crommentui]

For many of our clients performance is key. With the list of tags growing, going server to server could be an excellent solution for maintaining/improving site performance. Tealium has a server to server feature as described in this post: Server-to-Server Configuration

Server to server has been replaced by EventStream Connectors. 

Before advocating Tealium's server to server feature to our clients I have the following questions:

1. When should a client consider server-to-server?
2. Are there any success stories / insights that you can share?
3. Are there any additional costs involved?
4. Which tags are supported? (is the list in the community post up-to-date?)
5. Is there a roadmap for server-to-server?
6. What features/functionality do you lose when using server-to-server?
7. Typically pixels use third party cookies for storing a visitor id. This information is not available server side, so an alternative to the third party cookie storage is required, correct?
8. Are extensions supported on a server-to-server tag? For example an extension that sets a â google_conversion_labelâ based on the page_type?
9. How would you test and debug a server-to-server tag? Itâ s a long list of questions, but I think this topic deserves thorough consideration.

Thanks in advance for answering my questions!

Regards, Koen.

[ty_gavin]

Hi Koen, I'll have to refer you to your account manager for more specifics (cost, etc), but I can answer a few of these. For #1, the main use case for server-to-server is pixel reduction. Let's say you have 3 or more Analytics Vendors on your web site and you want to reduce the 3 tracking calls to 1 Tealium DataCloud tracking call. For example, you have SiteCatalyst, Google Universal Analytics, and your own internal data collection server. With server-to-server, one DataCloud tracking request client-side can send data to all 3 locations server-side. For #4, only the most popular analytics tags are currently supported: SiteCatalyst and Google Universal Analytics. Although with the Tealium Generic Tag you can send data to any data collection server. For #7, you're right. The reading the 3rd-party cookie client-side is required in many cases -- this makes it less likely you would want to run other tags (non-analytics) pixels server-side. For most of these use cases, Tealium's AudienceStream server-side connector integration may be a better way to go. For #8, extensions run client-side to manipulate the data and then the data layer data points are then mapped to the right place. Depending on your use case, you may be more interested in AudienceStream badging and integrations with DoubleClick (DFP) in AudienceStream. For #9, I recommend using Google Universal Analytics for debugging. You will need to: (1) Look at data layer that is sent (in DataCloud tag in the browser) (2) View report in your analytics tool to confirm it arrived For AudienceStream, there is a set tools available for real-time debugging and reporting of your data layer.

[adam_leary]

BTW that URL doesn't work and states "you don't have sufficient permissions to view this page". Has this information moved?

[kathleen_jo]

Hello @adam_leary. Great question. The information has moved. Let me see why and get back to you. Stay tuned...

[kathleen_jo]

Hello again @adam_leary. Okay the server to server configuration has been replaced by EventStream. Please find information on EventStream Connectors here:

• https://community.tealiumiq.com/t5/Universal-Data-Hub/EventStream-Connectors/ta-p/13889

Let me know if you have any other questions. 

[adam_leary]

Thanks @kathleen_jo - this is helpful.

[kathleen_jo]

My pleasure @adam_leary!