Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
BACKGROUND AND BENEFITS

...

1. Create a Service Request to Oracle in order to enable 1st party tracking for you 
2. Create an Eloqua specific subdomain through your DNS settings for your main domain, e.g. tracking.example.com (first-party cookie domain)
3. Add one new line to Eloqua tracking script code on your website including the created Eloqua specific subdomain (see Oracle guidelines):
_elqQ.push(['elqUseFirstPartyCookie', '<tracking.example.com>']);
4. If you are using SSL, your tracking domain needs to be configured as a secure microsite in Oracle Eloqua and must have an SSL certificate associated to it (in practice either a "wildcard" certificate of your main domain or a new certificate purchased for the tracking domain).
5. You need to update the form action on all forms hosted outside Eloqua to use your tracking domain, for example: https://tracking.example.com/e/f2 instead of Eloqua based domain like: https://s123456789.t.eloqua.com/e/f2. Without this, individuals filling the form won't be getting proper 1st party cookie. 

NOTE: Eloqua tracking script is only necessary for pages not hosted by Eloqua, so there is no need to add it on Eloqua landing pages. According to Oracle supprt: "The Eloqua microsite /landing page is functioning differently, they are tracked automatically by Eloqua without tracking script embedded, and will drop Eloqua GUID and Subdomain GUID automatically. 
.
DOCUMENTATION

...

.
VERIFYING EVERYTHING WORKS

...

4. You should see a cookie set to your own primary domain with name ELOQUA as well as a cookie set to eloqua.com domain with name ELOQUA
.
B. Form Tracking
Follow steps 1-4 in previous section

...