I'm a web, database, and network architect based in NYC, with specializations in the financial services, publishing, and SaaS sectors.
I build complex Marketo integrations for companies large and small... and can make Marketo forms and emails do things you never thought possible!
Check out my blog at https://blog.teknkl.com, which has Marketo-specific technical insights you won't see anywhere else, along with wider topics from my programming and systems work.
If you have a closed universe, it can work.
We’ve done this in a few different cases:
choosing from K-12 schools in the US (calling a remote service that has that data)
choosing...
Pre-Fill gets the value from the lead record. It’s doubtful there’s anything wrong with that process. You’ll have to link to your page so we can look at it more deeply.
A CO import cannot create new leads.
If you’re upserting COs that potentially relate to leads that do not yet exist, you must either
(1) upsert all the leads first (perhaps only ...
The string value “default” is valid for any string field — it’s not special. Marketo will Pre-Fill with this value the same as any other. So it’s likely you have a Smart Campaign s...
@adele_briggswrote:
thank you for this additional information. the endpoint was the Rest api. I am wondering now if they did not have the form ID included. It is a bit of a hodgepo...
You have to show the Activity Logs where your custom Consent Date is actually updated.
It’s obviously possible to have a Date field set in the future, well after the Updated At.
2 typos in your choices. Compare them carefully to the stored values.
PS. Extra (related) question, but not a concern like the above is: I'm using the Webinar Date Code in my ale...
Your HTML is broken. You can’t nest <style> tags.
<style>
<!--Variables END-->
<style type="text/css">
@font-face {
font-family: "Metronic Pro Black";
sr...