Tealium Learning Center

Thanks, Mark. Exactly what I needed. ... View more

Hey Dan There are a few steps to go through in terms of getting a user added to your CM account as a user. The steps in the documentation cover that well. Once you have that sorted, create a floodlight activity for the offline conversions you want to push. The ID of this is the Floodlight Activity ID in the connector, the Floodlight Configuration ID is the ID of the Advertiser in Campaign Manager. We tend to run a parent Floodlight Config Advertiser, and then link channel-level advertisers to this, so we have all the Floodlight activities in one place. Your match IDs are where you need to look at what you have available. If you are passing conversions for use in SA360, then use gclid as your match ID. We have seen the highest match rate when using gclid (90%+). Where there is no match, we get back a ‘GCLID not found’ error from Google but can see the gclid populated. For non-SA360 conversions, there are a few – imperfect – options. If you have a device ID, try to make use of that. The encrypted user ID is only available in some territories – it used to be in the Doubleclick Data Transfer files, but is obfuscated in the EU due to GDPR, so may not be available to you. We have tried passing an external user-level ID as a match_id into floodlights on-site, and then into offline conversions through the connector, but this has much lower match rates than with gclid. NB: If you select a given ID, and then pass through an action that doesn’t have that datapoint populated, the connector will fail. It's a bit of a mixed bag, so you might have to find a combination of approaches that work well for you. ... View more

Hi Jason. You can control the events that get sent to Facebook and trigger them off specific criteria – such as different tealium_events. First off you’ll need to turn off the auto page view trigger – use data mappings in the tag to do this: This then allows you to use Event mapping to control what FB event you want to send, whether that be standard ones (as you’ve described with Page View and Subscribe) or custom events. To trigger these, you use an existing data layer variable that allows you to distinguish the different events you want to trigger on. In the screengrab below, I'm using event_name for decisioning. If you don't have one datalayer variable that could be used for all cases, make a new one, e.g. fb_event_name and set the right values to it with extensions. In the example below, you can see a pre-existing mapping to SubmitApplication we have, and I've mocked up what a Subscribe event might look like. With this approach, pixel ID would stay the same and you would generate events only when you explicitly want to. Hope that helps. ... View more

@oscar_fernandez, did you manage to resolve this? We are seeing the same thing with a new implementation of gtag. We're looking at bundling the gtag global snippet with utag.js, then having child events fire for both Doubleclick and Analytics.  Custom dimensions are failing in GA. ... View more

Thanks, Rui Pedro. That worked. Phil ... View more

Hi Mark. That makes perfect sense. Thank you. ... View more