What Atlas reads from Typeform

DataDetails
SubmissionsEvery form your visitors sent, from your full history, kept current by webhook.
AnswersQuiz and application answers, on the person who gave them.
EmailThe email on each submission: the strong ID Keyring joins on.
Visitor IDThe Atlas visitor ID, carried in as a hidden field, that joins the visits before the form.

How a Typeform record finds its buyer

  1. 1The pixel records the visitsThe Atlas pixel on your site records each page view and the ad click ID, and remembers a visitor's first touch for 90 days.
  2. 2The form carries the visitor IDThe visitor ID rides into the Typeform as a hidden field, so when they submit, those anonymous visits join the person.
  3. 3The email joins the restThe email is a strong ID, so the submission joins the buyer's bookings, calls and Stripe payments on the same email.
  4. 4Paper Trail credits the saleThe buyer's path runs from the first ad click, through the form, to the payment, and the sale is credited under six attribution models.

What it feeds

Limits

  • A submission joins the visits before it only when the form carries the Atlas visitor ID as a hidden field. Without it, the submission still joins its buyer on the email.

Questions

What does Atlas read from Typeform?

Your submissions and their answers, with the email on each and the Atlas visitor ID when it rides in as a hidden field, kept current by webhook after the first import.

How does a Typeform tie back to the ad?

Through the visitor ID. The pixel remembers a visitor's first touch for 90 days, and when they send a Typeform carrying their visitor ID as a hidden field, those earlier visits, ad click included, join the person.

Most of our buyers book through Calendly. Does their ad click still count?

Calendly does not carry the visitor ID, so ask for the email in a Typeform first, with the visitor ID as a hidden field. The earlier visits join the person, and the booking joins them on the same email.