Using Lead Status to segment in RTP

[Anonymous]

Hi all,

I am trying to set up an RTP segment using the "Lead Status" field.

In Marketo, I have created a revenue model with transition rules set in an operations folder.

(Thanks to Josh Hill for his words of wisdom on that)

Sessions – The Marketing Nation Summit, April 13-15, 2015 – Marketo

The revenue model includes two stages that are aligned to different streams in an engagement program.

1) "Far" Newsletter -> Stage entered when added to the "Far" newsletter.

2) "Near" Newsletter -> Stage entered when added to the "Near" newsletter,

or stream is changed from "Far" to "Near" after reaching a certain point total.

※ "Far" and "Near" refer to how soon a customer intends to get married, as this site focuses on bridal jewelery.

I would then like to use these stages to segment users in RTP and send different campaigns.

In RTP, I have used the rule "lead status is xxxxxx" to target those in each newsletter.

When testing this method, I have been unable to see the number of segment matches rise in RTP.

The lead status has been changed correctly in Marketo, and the smart campaign managing the lead status data change

also shows that the members have been processed correctly in "Results".

Is it correct practice to be trying to segment in this way? Or is there something I appear to be missing?

Any advice would be appreciated.

Thank you,

Luis

[Josh_Hill13]

Does RTP require an overnight data sync? Probably should not.

Did you select known or Anonymous records?

RTP Segments - Marketo Docs - Product Docs

[Anonymous]

Hi Josh,

Thanks for your input!

There has been no overnight rise in the number of segment matches for yesterday.

I had not defined whether the lead was known or anonymous, so I added this to the segment settings.

1) Lead is Known

AND

2) Lead Status is xxxxx

I've added two test users and transitioned them into the "Far" and "Near" Engagement streams.

After waiting two hours, there has been no increase in the number of RTP Segment matches for either.

I'll have another check later on and post if the matches count appears to have increased.

Kind regards,

Luis

[Jim_Thao7]

Please share what you've tested and your data validation for that test.

Example:

1. Visit the landing page

2. See if you match the segment (must match all segment criteria)

3. Build smart list in Marketo (must match all segment criteria in RTP - use the most similar filters in Marketo)

[Anonymous]

Hi Jim,

Thanks for chipping in!

My testing method is as follows:

1) Create a new test user directly in the lead database.

2) Add the test user to the "Far" stream of an e-mail engagement program from the lead database screen with a single flow action.

3) Check that the lead status is "Far".

4) Check that the Revenue Cycle Model stage is "Far"

5) Check whether or not the number of matches for the "Far" RTP segment has increased.

※Yesterday the number of matches for this was 5 and it did not increase after my testing.

Some data is passing through, I'm just not sure what.

※ Repeat the same process for "Near". The matches count for this was 0, and remained at 0 after testing.

I also created two smart lists in Marketo as per your suggestion, with the condition "lead status is xxxxx".

Both lists accurately show all leads in each stage, including my tests.

Kind regards,

Luis

[Jim_Thao7 · Accepted solution]

At which point do you visit the page with the RTP script to get a segment match?  At which point in time do you get cookied by Marketo or RTP? There seems to be quite a few testing steps that are missing here.

These two platforms, although both owned by Marketo are separate and contain separate DBs. 

[Anonymous]

Hi Jim,

Thanks again for your input.

I've changed the testing method to include interaction with the website to ensure the user is tagged.

Note: The RTP script has been included on every page for the website I am dealing with.

1) Delete all cookies in the browser to ensure a clean start.

2) Create a new test user using a Marketo form on the website.

(I am guessing that by visiting the site, the user has been cookied by RTP since the script is included on every page)

3) Add the test user to the "Far" stream of an e-mail engagement program from the lead database screen with a single flow action.

4) Check that the lead status is "Far".

5) Check that the Revenue Cycle Model stage is "Far"

6) Go back to the website and visit another page which has the RTP script.

(I have done this so hopefully RTP then realises that the user has been moved to the "Far" stream

and can look up the updated lead status)

7) Check whether or not the number of matches for the "Far" RTP segment has increased.

So far I haven't seen any increase in matches, so I am definitely doing something wrong.

I'd imagine there's at least some kind of connection between the two databases, as you can define a segment using

a few fields used in Marketo including "Lead Status". I'm not sure how I could trigger an RTP match for that without the user visiting the website at some point.

Kind regards,

Luis

[Jim_Thao7]

1) Delete all cookies in the browser to ensure a clean start.

2) Create a new test user using a Marketo form on the website.

(I am guessing that by visiting the site, the user has been cookied by RTP since the script is included on every page) --- Please make sure that you become known in Marketo and RTP.  You can check the Leads/Visitor tabs in RTP to see if you become known.

3) Add the test user to the "Far" stream of an e-mail engagement program from the lead database screen with a single flow action.

4) Check that the lead status is "Far".

5) Check that the Revenue Cycle Model stage is "Far" --- You can probably skip this step since this won't matter as all you're interested in is the Lead Status.

6) Go back to the website and visit another page which has the RTP script.

(I have done this so hopefully RTP then realises that the user has been moved to the "Far" stream

and can look up the updated lead status) --- Give this some time, do not do it immediately.  I noticed that it takes a while for all of the data to sync back/forth.  I'd say 15 minutes at least.

7) Check whether or not the number of matches for the "Far" RTP segment has increased.

Other than that, the test seems pretty good.  Do it a couple of times to ensure it's working properly and if it doesn't work, keep at it and look to see where it can be updated/improved on.

[Anonymous]

Hi Jim,

I conducted this test paying attention to your points, and alas the matches count raised as it should!

Thanks for your advice, it is very much appreciated.

Hopefully getting campaigns up and running for these segments will be a smoother process!

Kind regards,

Luis