Sanford! I would not have believed it, had you not included that URL (https://pages.vaneck.com/lab-runtime-segmentation-01.html?State=ny)!
The part I can't figure out is how to create the segments to look at the URL. For example, I want to do the same thing as what you demonstrated, but with my PPC ads, and the same landing page but differentiated in the URL to display different content:
But in order to create the segmentation, I have to create segments, and the segments require a smart list and I can't find a way to look at URL parameters in the segment. Surely I'm missing something because your example works exactly the way I want to do it. Any ideas or help would be very much appreciated!
Your URL parameter name is the name of your segmentation. For example, we're using this same "real-time" approach for delivering country-based content. So the URL must contain a segmentation name for the url parameter. For example: page.com?CountryParam=us
Dan and Sanford... thanks so much for replying!
Ahh... so not sure if I'll be able to use this cool ability with PPC... ?
Google Ads generates a URL like this:
Your examples work with just one parameter after the question mark, but the source wouldn't do me much good. I would need to leverage the campaign and ideally the campaign and the term.
My best guess is to try something like this and see if Marketo can parse that out of the end of the URL:
Have either of you seen it done something along these lines? Just curious. Thanks!
Any URL parameter will do, doesn't have to be the first!
And you can pass different segmentations (one segmentation per param).
But because of the way Marketo works (with or without this method) only one segmentation applies to a given piece of content. (Though there are ways to get tricky with this by using JS blocks.)
I am in a similar situation and would like to know - how you created segments for the url param, for which no field exist(to filter).
No need for a specific field, your Segment Smart Lists can all check for non-empty Email or something generic like that.
And btw we have a slew of LPs using this technique in production in exactly the same way Christine describes, letting users view different product groups on the same LP by clicking different email links.
We use a Velocity script to check if they are already hard-segmented in the database; if not, they can soft-segment themselves, which we then commit to the database afterward.
I just tried setting this solution up and might've stumbled across the snippets not being necessary - just the segmentation?
I'm using this in a guided landing page, that didn't yet have any snippet section added in the template... Before I started adding the snippet piece into my template, I tested something: with a segmented html text area, the variable passed in the url perfectly fine! I checked in an incognito browser, and I'm not catching any issues. I'd thought the snippet was a key component for it to work... but seems it works this way as well.