Form field interaction - technique to reduce excessive calls

Avatar

Avatar
Ignite 1
Level 2
stephenr6438258
Level 2

Likes

14 likes

Total Posts

20 posts

Correct reply

3 solutions
Top badges earned
Ignite 1
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Ignite 1
Level 2
stephenr6438258
Level 2

Likes

14 likes

Total Posts

20 posts

Correct reply

3 solutions
Top badges earned
Ignite 1
Validate 1
Boost 5
Boost 3
Boost 10
View profile
stephenr6438258
Level 2

25-08-2017

Hello,

We've received a requirement to track website form field interaction and also collect some of the values being entered (non PI), passing them into Analytics.

Basically need a way to see how far the customer progressed through a check out process.

Currently each field sends a direct call rule (s.tl) into AA for each field, however as you can imagine our volume of network calls is rising. 40+ questions!

I wanted to understand if anyone has any tried and tested methods of collecting values and monitoring the progression through fields?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,340 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,340 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

25-08-2017

Hi

DTM does have a few built in events for forums (focus, blur, submit, change). If you've already got direct call rules setup and they are allowing your to track the actions you'd like, you don't need to change to the default events. As for the rise in server calls, that is a side effect of tracking each action in the forum. A few ideas I have for reducing your volume of tracking calls:

  • Break the form into pages and send a single call for each page completed
  • If the form can't or doesn't make since to be broken into pages, you could fire a beacon for each group completed (fire one beacon for each group of information rather than each field).
  • Write a script that increments as each field is completed/validated and send that beacon before the user leaves the page.

Hopefully this gives you a few ideas.

Thanks,
Jantzen

Answers (0)