Landing Page Data Lookup?

[Anonymous]

My team wants to have have a landing page that will know what store location the customer should go to based on an ID in the url.

Store Name

Address

Phone

The leads that get here from Market emails will be easy to do. The ones that get here through 3rd party sites... How would I do this? I know I need a lookup table but now I need some advice on my best move.

Thanks!

[SanfordWhiteman]

There is also a 3rd way, possibly the easiest of all if your lookup table is small (the definition of "small" depends on your taste for using the Marketo LP UI, though it must be <= 100).

Create a segmentation called storeid.  Create an HTML widget.  Segment the widget it by ID and set the contents accordingly.  Then when someone passes ?storeid=200 the corresponding segment will be displayed.

[Andy_Varshneya1]

Similarly, and this would be a little overkill but may be justified if you see this part of the process growing, but you could also do this with a custom object.

[Anonymous · Accepted solution]

There can be 2 main options...

Option 1:

Using a webservice for 'lookup' and AJAX for rendering in the landing page.

You can use the example from

http://www.w3schools.com/php/php_ajax_livesearch.asp

and retrofit it to your needs.

The 'lookup table' is stored in a xml file in this case. http://www.w3schools.com/php/links.xml

There is a 'web service' which accepts a parameter 'q' and returns the matching records. Like,

http://www.w3schools.com/php/livesearch.php?q=javas

and

http://www.w3schools.com/php/livesearch.php?q=dat

and so on.

In your case, it will be the id from the url of the landing page.

On your Marketo landing page, you will write AJAX code which will,

a> Grab the id from the url

b> Query the 'web service' with that id. The webservice will return the data looked up for that id.

c> The AJAX code will parse the xml returned and display on your landing page at appropriate places.

Instead of xml, you can use JSON object too.

Pros:

1> If the lookup data is sensitive, this might be the way to go.

Cons:

1> You will need a webserver with server side code development in this case php.

Option 2:

Using Javascript Array / Object

If the 'look up table' is not too big and not too sensitive, you can have it coded as a javascript array or object on the landing page itself and look up the values directly from the array. Thus your landing page will be self-sufficient.

Cons:

1> Do not use if the look up data is sensitive. View html source can show the entire look up table.

2> If this lookup table is used in several landing pages and there are 'frequent' changes, you will have to modify each landing page separately. But you can potentially use Marketo tokens or files to avoid it.

Hope this helps

Rajesh

[SanfordWhiteman]

Also, since the values (store names) are presumably public, you could obfuscate the object keys (IDs) by using a hash of the ID for the lookup, if that matters.

So someone would see that {seemingly_random_id_1} goes to the Toledo store and {seemingly_random_id_2} goes to the LA store, but they couldn't figure out the original query param.

[SanfordWhiteman]

Yep, I was alluding to your #2 with the lookup table stored in a file asset.

[SanfordWhiteman]

I don't understand the need for RTP as described.  How big is the lookup table?

[Anonymous]

There is always a need for RTP

[Anonymous]

For this landing page it would be 150 stores. So 150 IDs matching name, address and phone.

[SanfordWhiteman]

I'd put that in a separate JSON file (Mkto asset) -- or even self-executing JS script file -- and pull it in like Rajesh pointed to. It doesn't sound like the ID nor store info is private.

If you package it as a JS file, you can include the script in the page without needing to deal with any Ajax logic.

[Anonymous]

Yep, I like it! Thank you both!

[Anonymous]

I think that you can do this with our RTP module, that would be the easiest way.  It's an upgrade but well worth it!

[Grégoire_Miche2]

This is exactly the kind of things that can be done with RTP.

-Greg