Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Hi Keiji,Generally I would set up a program that captures your source in the Person Source / Lead Source field (it is named a bit inconsistently in the UI but is the same thing). Information you can use to identify the correct source is:Any utm source data you capture from form fillsPerson being cr...
Nope, the OnSubmit has the dispatcher call upon the backend to execute the API call. Looks like the webteam found a configuration error in the dispatcher which should be fixed tomorrow. Fingers crossed.
I hope the collective experience on the community can help identify the root cause for something we are running in to.I have a customer who, for reasons that are not relevant here, has two production Marketo instances and for some of the webpages on their website forms need to be submitted to both i...
That was exactly what my initial response was. Taking a Marketo instance with data already in it is a sure recipe for duplicate nightmares. The big gotcha there is that the native sync doesn't use email address as the unique record key, but the Dynamics record id. As your existing Marketo database ...
Totally agree with the alternative approach. If you have multi-purpose PMCF fields set up where one is a date field I would actually opt to use this, rather than set up a dedicated field on the person for just this campaign.
Couldn't agree more. You cannot keep scores adding up into infinity, it is equally important to recognize inactivity and let scores decay accordingly.
A screenshot would be helpful here, as we are only guessing at what might be wrong. My first question: Did you approve your email yet?
We have some good experience with cm.com as well.
I agree with @Darshil_Shah1 here. This sounds like the least attractive way to achieve your end goal. The two options that seem the most effective in the situation:Clean up the SFDC database with the sync on. Any clean up in SFDC will be mirrorred in Marketo, merging historical data as you go along ...
You are totally correct @Michael_Florin . Coincidentally I had raised this exact point with the product team as well. I see they have picked up on this thread already, so I am sure this will be improved in the next release.