DTM: TypeError: _satellite not defined

Avatar

Avatar

russkalchbrenne

Avatar

russkalchbrenne

russkalchbrenne

15-10-2015

I'm adding DoubleClick Floodlight tags to specific campaign pages.  We have a separate tag for 6 pages. I've created Page Load rules for each page since the ids in the tags are different.   All rules are working but the purchase receipt page rule where I need Data Element.  When the rule fires I get a JS error in the console: TypeError: _satellite not defined. 

In the Javascript/Third party area I'm using  Non-Sequential HTML:

<script type="text/javascript"> document.write('<iframe src="https://1346129.fls.doubleclick.net/activityi;src=12345;type=xxx555;cat=xxx555;qty=1;cost=' + _satellite.getVar('Purchase Amount') + ';u1=monthly;ord=' + _satellite.getVar('Purchase ID') + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>'); </script>

I removed the script tags and switched to Non-Sequential JS and the page wouldn't load.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

mhelbling1

Avatar

mhelbling1

mhelbling1

15-10-2015

Hi Russ,

Usually when _satellite is throwing a not defined error that means there is trouble with the loading of the head embed JS.

Check your confirmation page to see if that is there, and isn't referencing an incorrect ssl status (http vs. https). It is best not to put one in at all.

Non-sequential HTML should be fine to load the tag once you resolve the _satellite not defined issue.

A non-sequential JS won't work in this case since you are using a document.write in your script.

Another possible test you can do is to load the Floodlight tag as a sequential HTML. If that resolved the _satellite issue then there is a problem getting the data elements to populate in the iframe created by the non-sequential HTML.

Hope that helps,

Michael

Answers (2)

Answers (2)

Avatar

Avatar

stewart_schilli

Avatar

stewart_schilli

stewart_schilli

15-10-2015

MYOHMYOHMYMOTECH !!!     This is the exact issue that I was having.  Thank you for the answer!

Yes, by dumping the old 3rd party floodlight tag into a Non-Sequential HTML container my problem was solved. 

Avatar

Avatar

russkalchbrenne

Avatar

russkalchbrenne

russkalchbrenne

15-10-2015

Thanks Michael,

Switching to Sequential HMTL worked.

Russ