SOLVED

Implementing Global Forms - capturing fields - parameters vs. token

Go to solution
Anonymous
Not applicable

Implementing Global Forms - capturing fields - parameters vs. token

Hi all,

We are implementing global forms at our company and we're debating a bit on whether we want to capture hidden fields such as lead source as a token on the program level vs. using parameter URLs.


We see in some instances, using the token on the program level is easiest. However, for other cases, that's not ideal (don't want to make numerous programs), so want to some as parameter URLs. We are questioning whether we even want to do some one way (token), and some the other (parameter), or if we should just mandate we do it all 1 way (parameter).

How does everyone else do this? Or do you have any processes/tips on a better way to handle this?

Thanks!

Tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10

Re: Implementing Global Forms - capturing fields - parameters vs. token

See

Solutions to capturing snapshots of url parameters in MKTO fields associated with Programs?

Program level tokens are probably the way to go if you plan to create a Program Template and clone it a lot.

View solution in original post

1 REPLY 1
Highlighted
Level 10

Re: Implementing Global Forms - capturing fields - parameters vs. token

See

Solutions to capturing snapshots of url parameters in MKTO fields associated with Programs?

Program level tokens are probably the way to go if you plan to create a Program Template and clone it a lot.

View solution in original post