Ensuring Source Codes "Stick" from Facebook/Twitter Ads

Options
In the past, we have noticed that our source codes are frequently not recorded on Luminate interactions (in particular surveys and action alerts) when the source is from Facebook and Twitter. We are about to launch a Facebook acquisition campaign, and it will be very important for use to know the specific ad that is the source of each survey/action alert interaction. While I know it's not possible to have 100% of the source codes recorded due to technical issues and settings on individual browsers, it seems to happen quite frequently, leading me to believe the issue might be with Facebook itself.


Has this happened to anyone else, and are there best practices for ensuring the most success in recording source codes on our interactions?


For instance, I'm wondering if the link construction we use in the might impact whether the code is stripped off. Our base URL can be any of the following. Perhaps one is more likely to preserve source codes than the others?

https://secure.audubon.org/site/Advocacy?cmd=display&page=UserAction&id=1913

http://www.audubonaction.org/site/Advocacy?pagename=homepage&id=1913

http://www.audubonaction.org/site/Advocacy?cmd=display&page=UserAction&id=1913
www.audubonaction.org/site/Advocacy?id=1913

 
Tagged:

Comments

  • I'd recommend installing a facebook pixel on your page, and either create custom conversions (easy but less flexible) or customize the code to track standard events (harder -- you'll need to know how to use S-Tags -- but is much more powerful).


    Other than that, LO respects s_src and s_subsrc (and these are supposed to persist after the URL changes to remove them). It's also a good idea to include UTM tags for google purposes (and the extra data in the URL is useful for retargeting ads). One other thought would be to make a URL shortcut in LO, and maybe add interest groups or other stuff that will be added by LO whenever someone hits the link.

    Here's a full example URL for you with source, subsource, and UTM tags. I'm using your page ID as the campaign, but you could use anything you want that would make sense in the reports...

Categories