Dynamic Landing Page for Sales Team

[Demeter]

Hello Community,

I believe I'm overthinking my logic and it may not be possible to achieve it my way.

Email is sent -> lead (who we already have certain criteria for in DB) clicks link -> goes to LP with a form -> completes form -> information emails sales rep.

Goal: to have one dynamic landing page that displays their associated regional reps information with a form that upon completion, will be sent to the rep. Each rep covers a specific region, which is already established in SFDC so we would know which reps info to display

Short of creating different LPs for each sales person, is there a way to create one LP and have the leads' sales reps information display based on, let's say, the leads identifying state?

I'm looking for best practice and cleanest way to accomplish this without so much clutter. Working on an instance that has already had many hands on it and is cluttered.

Thanks in advance!

[SanfordWhiteman]

You definitely don't need more than one LP.

How many different inputs are there? You say "state" - do you mean the 50ish US States? (The number of input variations matters for finding the best solution.)

[Demeter]

There are 50 US states are broken down into 6  regions. Each sales rep has certain states in their region.

i.e Sales rep 1 has Georgia, Kentucky, New York - When a lead clicks the "reserve appointment" link in the email, should go to the landing page where it displays that sales reps information. Then the triggers would take over sending him the request.

Appreciate the help @SanfordWhiteman 

[SanfordWhiteman]

But you don't know the person's State until they choose it after landing on the page, correct?

[Demeter]

actually we do know the state. It's already in the DB

[SanfordWhiteman]

So create a Segmentation and use Dynamic Content!

[Demeter]

would you mind detailing the flow? 😑

I have created the LP with segmentation by sales rep. The dynamic LP part is working, just not the link to direct to the right page

my logic is: if Lead X is from State Y and clicks link-> Display associated sales reps Z information on LP

[SanfordWhiteman]

---

I have created the LP with segmentation by sales rep. The dynamic LP part is working, just not the link to direct to the right page

my logic is: if Lead X is from State Y and clicks link-> Display associated sales reps Z information on LP

---

Like Michael, I’m confused about why you’d be referring to “the right page”? There’s only one page. It has Dynamic Content (i.e. a block specifically set w/different content per segment).

If you send a link to that LP to someone in Segment A — and, of course, the link is tracked — they’ll see the content for Segment A.

[Michael_Florin · Accepted solution]

If there is only one page which is dynamic by Segmentation, you don't need different links. There is just one. (Or do I not understand the question correctly?)

And btw: You can enforce a segmented view by using URL parameters:

www.example.com?segmentationname=segmentname

[Demeter]

Thanks Michael. In the end I got it working. As I mentioned, I was overthinking the process but it's good to know folks like yourself and others are around to have input. No one to really bounce things off of in office 🙂

[Demeter]

Yes there is one dynamic LP, segmented by sales rep that displays their information. The goal would be to use 1 link, but how does the link know the "lead" is from state X and sends it to the LP that will display the correct reps info?

That's where I am getting lost. Am I missing a step somewhere in the link setup? 

and TIA @Michael_Florin 

[Darshil_Shah1]

When the Munchkin session gets associated with a person's record (which it would when they click the tracked LP from the email as the mkt_tok query parameter in the tracked link will associate the request with the person's segment) they should see the LP content as per their respective segment. Since you're routing people to the LP from an email, this should be sufficient for people to see the correct content per the segment into which they fall.

The other way would be by including the query parameter to specify the segment in the URL parameter - the person would see the content as per the segment mentioned in the QP even if there isn't a Munchkin session associated with the person's record.

[SanfordWhiteman]

---

When the Munchkin session gets associated with a person's record...

---

It actually doesn't rely on Munchkin. For a new session, Munchkin has not yet initialized — there is no Munchkin cookie — at the point the correct page content is returned. Only the mkt_tok is strictly necessary.

[Demeter]

Thanks @Darshil_Shah1 - Going to test it out here shortly