Marketing wants to know how many product views, orders, etc. came from
visits originating from a specific email or link.For example:Marketing
sends 1000 emails with the link
www.mysite.com/promo1?campaign="free_ship_email"150 users click that
link in the emailDuring those 150 visits, there were 320 product views,
145 cart adds and 12 orders resulting in $3000 in sales.How do I report
on this in Workspace? I am guessing I need to capture this value in an
evar, which expires after visit, and add a...
I work for a global company and we have 25 different countries that need
reporting. We have three sites, each with a dev and production report
suite. This means a possible 50 report suites per site, totaling 150.
When I click on the report suite selector a long list of report suites
appears with no organization. It would be nice if there was some
grouping for each site. Instead of 150 report suites, I would see three
sites. Once you click on the site, the folder expands to show the
It seems a best practice to track pagename is create a data element
using "didigtaldata.page.pagename" Are there other standard values
captured this way, like digitaldata.page.url? If so, how do we find out
what they are?
I need to track internal search terms, so I created a rule that triggers
when a search is submitted. I also have a global page load rule to track
all pageviews. Now, when a user submits a search, there are two rules
firing. One s.tl() rule for the search (sending search term, number of
results and username) and a different s.t() rule for the page load
(sending page name, URL and username)Is this a best practice, or is
there a way to simplify this process into a single rule/server call?
In the implementation guide, the product variable is complex. Is this
the case with Launch? For tracking product views, sku#s, price, etc.
should these all be different props/evars? or one product variable?
Please help me understand the best practice for this use case. Thanks.