Change Program Status in Marketo Impacting Lytics | Community
Skip to main content
Shane_Rourke2
Shane_Rourke2
New Participant
February 10, 2023
Solved

Change Program Status in Marketo Impacting Lytics

  • February 10, 2023
  • 1 reply
  • 1141 views

Hello Community, 

 

Does anyone have Lytics integrated with Marketo for audience management? 

 

We recently had a program that marked leads as a success (clicked), which shouldn't have been. We fixed that on the Marketo end by removing and then adding back as a member. 

 

The data (success-clicked) that was passed over to Lytics from my understanding can't be changed. Does anyone have any experience with this or know of any workarounds that can be initiated on the Marketo side? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Danielle_Wong

I don't use lytics. So just some ideas... If no one has access to Lytics to remove the data points or to manually replace the wrong data and you really need the data to appear correct for reporting, can you create a duplicate program in Marketo and mark all those people correctly as clicked and have that program sync to Lytics. You'd exclude the old program from your report though. Of course there's likely other implications of this so I doubt this is the ideal solution. 

 

Ideal would be to update in Lytics directly.

1 reply

Danielle_Wong
Danielle_WongAccepted solution
Community Manager
April 11, 2023

I don't use lytics. So just some ideas... If no one has access to Lytics to remove the data points or to manually replace the wrong data and you really need the data to appear correct for reporting, can you create a duplicate program in Marketo and mark all those people correctly as clicked and have that program sync to Lytics. You'd exclude the old program from your report though. Of course there's likely other implications of this so I doubt this is the ideal solution. 

 

Ideal would be to update in Lytics directly.

Terms & ConditionsAccessibility statement

Loading footer...