Movable Ink

[Anonymous]

Does anyone have any experience using Movable Ink in their marketo emails? Interested in using the RSS feed feature and possibly the count down for webinar reminders. Thanks!

https://movableink.com

[Anonymous]

I'm interested to see what folks say. I hadn't seen the product before but it is a cool idea to host the content externally and update them.

Most email isn't read that many times, but it still might provide some kind of lift.

[Anonymous]

Right now I'm on-boarding Movable Ink. We haven't gone live yet, but the demo of the features look extremely promising. The roadblock I'm up against right now is identifying a Unique User ID field, essentially a Marketo primary key, to give Movable for effective functionality and tracking. Marketo support via web portal has been sending me through loops for 2 days. Their response is, "Marketo doesn't have a unique identifier." How can a database not have a primary key per record?

[SanfordWhiteman]

Of  course it does.  In fact, Marketo leads have three unique identifiers: the Lead ID (numeric), the Unique Code (alphanumeric), and the Unique Name (alphanumeric, based on the full name + tiebreaker numbers). No one who knows Marketo should be saying otherwise, unless perhaps the way you're planning to use the identifier is not possible.  Where is this field going to be exported/output, exactly?

[Anonymous]

Thanks for the response. Movable Ink generates code that dynamically changes email and content based on several different paramaters; time of day, IP, location, etc.

We aren't exactly going to export the field. Movable Ink is going to reference it in reporting opens. So essentially, I tell Movable Ink  the field that uniquely identifies a record, and they monitor when that person opens, how many times, and where that person is when they opened.

For now I'm going to use {{Lead.id}} to get the ball rolling. I have the option to change that if we see it's not correct or working.

[SanfordWhiteman]

I was using "export" in the dev sense of "publish a variable to another context" (not like "export to spreadsheet"). 

In any case, you should be better off with Lead ID than the others, which have very narrow use cases.

Still, I wonder about the whole life cycle here. Are you planning to use the REST or SOAP APIs to update based on a dump of their augmented data? Or are they claiming they can do the update from their servers?

[Anonymous]

They claim to be able to update from their end. No REST or SOAP API needed.

I want to be clear though...I should use {{Lead.id}} and not {{Lead.Lead ID #}}   ?

[SanfordWhiteman]

You can't update a Marketo lead who's been identified by Lead ID without an API call.

The only way to update a lead without an API call proper is to identify them via email address and do a form post (which is still essentially using the form's endpoint as if it were an API).

The token is {{Lead.Id}}.

[Anonymous]

Gotcha. I'm under the impression that Movable's analytics would supplement Marketo's analytics, much like Google Analytics.

Thanks for all your help. I'll most likely be back once we're up and running 8/1

[SanfordWhiteman]

Right, they could do whatever reporting they want based on the Lead ID. The question is how those reports could be actionable within Marketo without an integration of some kind. It's not like you're going to open up each Marketo lead and hand-type information....