In the words of Matthew Mcconaughey, "Alright, Alright, Alright!" Don't
know what I was doing wrong the first time around, but it's working now.
I had to modify the regexp a bit so that I could match the home page
with or without query string arguments. The pattern I ended up with is:
^[/]?[?]?[^/?]*$Thank you much! I'm so glad to have a good solution for
this. -Stew
Hi Joel, I'm still not getting it to work. Have you tried this yourself
and proven it to work? If I understand your suggestion, you are saying
that I should be able to create a PATH condition as INCLUDE ^\/?$ with
regexp turned on to detect the homepage of the website. Thanks,-Stew
Joel Stachowicz wrote... Hi Stewart, Using regex is probably the way to
go, but this use case is a bit more complex than it may first appear.
For instance, the match probably needs to take into account situations
like variations in protocol (http vs https), the actual homepage file
name (index.jsp), query params (?var1=1&var2=1), etc. in addition to
simply excluding alternate filenames like /page.html at the end of the
path. A simple match would be ^(https?:\/\/)?www.landsend.com\/?$ Use
the reg...
Thanks for the response, but it doesn't seem to work. Have you tried it
on your end? I put in exactly what you suggested and the rule still
fires on every page that begins with "http://www.landsend.com/"I've
tried a great number of regular expressions to no avail. I might add
that within DTM the little regex tester indicates that your solution
should work, but in application it does not. Thus my question.
Rookie question: How do I write a Path based condition that will detect
my homepage only? I'd like it to match :THIS:
http://www.landsend.com/NOT: http://www.landsend.com/shop/swimNOT:
http://www.landsend.com/products/womens-ruffle-thongs/id_265218NOT:
https://www.landsend.com/co/ShoppingBag.htmlor any other thing that is
not the base URL. I tried using "/" on the PATH condition but it didn't
work for me. I ended up creating a data element called "dtm_pathName"
which is the Javascrip Object "win...
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.
I'd like to know how to use the client's IP address as a rule condition
in DTM. I'd like to be able to include or exclude based on IP address
using regular expressions for matching. Is there a clean way to do this?
Thanks, -Stew
See Incident: Clearing a merchandising evar via process rule [Incident:
140404-000121] I tried writing a processing rule as such: If evar4
equals any (Shopping_Cart | PAGE_) then delete the value of evar4.
Pretty simple, yes? As it turns out, since evar4 is a merchandising evar
and it's value is set on the product string, processing rules cannot see
it or change it. I would like to be able to access and modify evars and
events in product strings from within a processing rule.
Enhancement request: It would be very useful to have the ability to
specify the order of execution of multiple tags on the same page. I
understand that you can’t (and shouldn’t) override the larger load
order, but if you have multiple bottom of page sequential HTML tags, it
would be great to be able to specify the order of execution. This
request stems from the fact that I have implemented individual rules for
each 3rd party tag (which allows me to enable or disable them at a
vendor level). As a...
