SOLVED

Marketo API - Pushing Landing Page Content for an LP that already has a draft

Go to solution
Conner_C
Level 2

Marketo API - Pushing Landing Page Content for an LP that already has a draft

I am working on automating some of our Landing Page content & Variables updating via the Marketo API, but cannot find documentation of how the API reacts to pushing changes to a Landing Page when that LP already has a draft.

  • When new content/variables are pushed, will the original draft be completely overwritten?
  • If the original draft is created by a Template update (and cannot be overwritten or discarded), will it refuse the new LP Content and preserve the original draft?

Thanks for your help!

//  Conner C

1 ACCEPTED SOLUTION

Accepted Solutions
Conner_C
Level 2

Re: Marketo API - Pushing Landing Page Content for an LP that already has a draft

07/23/18 Update: Wanted to add a bit more to this answer for this who come across it in the future:

Updates (via the Editor or API) to Landing Page Content, Variables, & Meta Data will all ADD to an existing Draft. Sequential API calls for updating Content, Variables or Meta Data will all ADD to an existing draft.

Update and Approval of a Landing Page Template (via the Editor or the API) will spawn a new draft for each Landing Page that uses that template. This new draft WILL OVERRIDE any previous drafts for that Landing Page.

So, in my case of mass updates via the API to both templates and Landing Pages, I will need to Update and Approve all templates first, and then approve the LP Draft that action creates. Then, I can update my LP Content, Variables & Meta Data, and approve that draft.

Original Response:

For anyone who comes across this post with the same question, I got confirmation form Marketo Support:

"If you update via API, the previous drafts are effectively discarded and the new draft is put into place.

Hence if people have any current drafts, and you update the template, their work will be lost. "

"You will need to update your templates, approve that change, and then update the Landing Pages, and then approve that change. "

This means that if you are updating content across Templates, Page Content and Page Variables, you will have to Update and the Approve for each section.

You will need to update your templates, approve that change, and then update the Landing Pages, and then approve that change.

View solution in original post

1 REPLY 1
Conner_C
Level 2

Re: Marketo API - Pushing Landing Page Content for an LP that already has a draft

07/23/18 Update: Wanted to add a bit more to this answer for this who come across it in the future:

Updates (via the Editor or API) to Landing Page Content, Variables, & Meta Data will all ADD to an existing Draft. Sequential API calls for updating Content, Variables or Meta Data will all ADD to an existing draft.

Update and Approval of a Landing Page Template (via the Editor or the API) will spawn a new draft for each Landing Page that uses that template. This new draft WILL OVERRIDE any previous drafts for that Landing Page.

So, in my case of mass updates via the API to both templates and Landing Pages, I will need to Update and Approve all templates first, and then approve the LP Draft that action creates. Then, I can update my LP Content, Variables & Meta Data, and approve that draft.

Original Response:

For anyone who comes across this post with the same question, I got confirmation form Marketo Support:

"If you update via API, the previous drafts are effectively discarded and the new draft is put into place.

Hence if people have any current drafts, and you update the template, their work will be lost. "

"You will need to update your templates, approve that change, and then update the Landing Pages, and then approve that change. "

This means that if you are updating content across Templates, Page Content and Page Variables, you will have to Update and the Approve for each section.

You will need to update your templates, approve that change, and then update the Landing Pages, and then approve that change.