DoubleClick Natural Search
Deploy the natural search tag to your landing pages
Customer support will send the DoubleClick Natural Search tracking tag to you. Have your webmaster post this tag within the body of each page that might receive traffic from a search engine visit.
// DoubleClick DART Natural Search Tracking Code
Bxxxxxxx;dcadv=xxxxxxx;sz=1x2;ord=' + ord + '?"><\/SCRIPT>'); }
To ensure accurate tracking:
The tag should be posted on every page that might receive traffic from a search engine visit, even vanity pages.
Post the tag close to the top of each page and within the HTML body tag.
The tag must be called upon every page load.
For questions regarding privacy, refer to the DoubleClick Privacy page or contact customer support.
Google Tag Manager makes it easy to manage tags from multiple Google sources, such as Google Analytics, Floodlight, etc. If you’re using Google Tag Manager for your site, follow these steps to deploy the DoubleClick Natural Search tag:
Go to google.com/tagmanager, sign in, and access your site’s container.
Create a tag that fires on every page load:
In the left navigation pane, click Tags.
Click the New button.
Replace Untitled Tag with a name that's meaningful to you.
For example, enter Natural search tag.
On step 1 Choose Product, click Custom HTML Tag.
On step 2 Configure Tag:
- Paste the Natural Search tag from DS customer support into the HTML field.
Select the Support document.write checkbox.
- Click Continue
On step 3 Fire On, click All pages.
Click Create Tag to save your new tag.
Follow the standard publishing process for Google Tag Manager:
Test the deployment from Google Tag Manager
If you used Google Tag Manager to deploy your tag, do the following to test the deployment:
In a Chrome web browser, visit the Chrome Web Store and install the Google Tag Assistant.
Visit your site through a natural search result.
Use the Tag Assistant to check that the Natural Search tag has fired.
Visit another page on your site. (Don’t click a search result this time.)
Use the Tag Assistant to check that the Natural Search tag did not fire.
Does this tag replace Floodlight tags?
The DoubleClick Natural Search tag is not itself a Floodlight tag. It is the tag responsible for tracking arrivals or visits from search engines and therefore is the essential part in DoubleClick Natural Search tracking.
Where on the page should the tag be posted?
The tag must be called every time the page loads. Posting the tag close to the top of the page within the HTML body tags is preferred. This will result in the most accurate tracking.
Can I use server-side include or some other language like Perl for the cache busting?
How long do I leave the tag up on the site?
The tag must remain in place for DoubleClick Natural Search tracking to occur. The tag should not be posted, removed, and re-posted repeatedly. The tag should not be conditionally written to the page.
The tag is negatively affecting my page load time. Can I take it down?
The tag is very small, about 2.4 kb, and it's designed to have a minimal impact on page load. DoubleClick Natural Search tracking cannot occur without the tag in place.
I don’t want a DoubleClick ad tag on my homepage. What can I do?
Search engines most often direct users to the homepage. Therefore, the homepage may be the most important location for the tag to be posted. If the tag is not present, DoubleClick Natural Search tracking cannot occur.
I have dynamically generated pages. Where should I post the tag?
The tag needs to render along with page content and load with each page request.
On what other pages should I post the tag?
Post the tag to any page that might be the landing page for a natural search visit. This includes vanity pages, temporary pages, or any associated pages that need to be tracked. For example, some clients maintain an About Us page.
On what pages should I include the exclusion parameter?
If you are running Paid Search campaigns, use this exclusion parameter on every page that the tag is used. If this is not done, natural search visits will not be counted. Implement the exclusion parameter like any other query string value. If no query string exists, add a new one. If your server does not support arbitrary exclusion parameters in the page URL, consult the implementation specialist for an alternate method.