Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
There is a system that stands between our CMS and Marketo. It handles domain blocking for trials, etc. This system is using a create/update REST api call. The problem we are seeing is, while the values that are submitted on the form are updating the lead record in Marketo as they should, other field...
Hi JB, that's very similar to an issue we've been seeing lately in some of our campaigns. In some cases not all status updates are syncing across. Wonder if it is a bug?? We're also following up with support.
I wonder if the order of statuses matter at all? The cases match exactly but the order e.g. Registered is above Trial Request in Marketo channel tags but vice versa in SFDC campaign advance setup.Nonetheless, thanks very much for your feedback. I'll followup with support.
Thanks for your response Greg.Here are those activity details:And this view shows one of the successful member status update of "Expiring" that did sync across to the campaign object, although funny enough, the previous or old status of "Usage Trigger 1 did not sync across across so there is no reco...
Hi everyone,We are noticing that in some cases our member status updates are not syncing to Salesforce.We have a channel with a number of tags or member statuses in Marketo that match what we have in the advanced setup for our campaign in Salesforce. In Marketo, under the program we have a number of...
Thanks for the input and tips here. I got rid of that second unnecessary alert email and now just use the same email in my email send flow step as in the alert flow step. As it turns out the my.tokens that were not populating because the token values, (e.g. paid seats data) wasn't being sent across ...
I'm definitely going to vote this one up . Seems like something that should definitely be available. Thanks.
Hi Greg,Thanks for your reply. The email trigger campaigns are indeed in that Rally Email Service program along with the assets and the my tokens.I'm wondering if the token values are not be sent across perhaps during the call.
To overcome the lack of cc'ing functionality we are using an alert to send a dupe to our sales team. The email (and dupe copy for sales) content contains a number of {{my.tokens}} the setup is like this:We created two versions of the email (1.) Sales copy (2.) Alert copy - however, the alert copy is...