How to report on same content used across different landing pages | Community
Skip to main content
February 15, 2017
Solved

How to report on same content used across different landing pages

  • February 15, 2017
  • 1 reply
  • 1937 views

Is there a way to report on how a particular piece of content is performing across landing pages? We have several programs that are using the same content pieces but had to clone each landing page to the particular program.  Is this the correct way to do this or are there better ways

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

Hi Dory,


Thank you very much for the reply.  Is it possible to create landing pages that do not exist with a particular program?  The query string makes sense (I am using that for our FB campaigns) but it seems I need to duplicate the landing page between program efforts.

Kenn

1 reply

Dory_Viscoglio
New Participant
February 17, 2017

Hey Kenn, your best bet would be to create a single landing page and utilize URL parameters in your querystring. This way, when you have a campaign that is triggered by a form fillout, you can have a querystring constraint on that trigger. You might also considering populating hidden fields via the querystring, although this isn't always necessary. There are tons of threads/recommendations about this in the community.

Accepted solution
February 17, 2017

Hi Dory,


Thank you very much for the reply.  Is it possible to create landing pages that do not exist with a particular program?  The query string makes sense (I am using that for our FB campaigns) but it seems I need to duplicate the landing page between program efforts.

Kenn

Dory_Viscoglio
New Participant
February 17, 2017

Hey Kenn, landing pages can live in the design studio so that they don't have to be associated with a specific program. One thing to make sure you do if you are housing your landing pages outside of a program, is to set the acquisition program via a smart campaign because it won't happen natively if the form/page are outside of the program.