developers.10x.in/docs/end-user/lead-capture-verification Published:

Lead Capture Email Verification

Lead capture campaigns can optionally verify a visitor email before the lead is stored, alerts are sent, webhooks fire, or campaign email rules run.

Modes

ModeVisitor actionWhen the lead is captured
NONENo verificationImmediately on form submit
EMAIL_OTPEnter the code from emailAfter code confirmation
EMAIL_REPLY_YESReply YES to the emailAfter the inbound reply is processed

EMAIL_REPLY_YES confirms mailbox/control-path access. It does not prove legal identity.

Sender Setup

  1. Verify the sending domain in the email platform.
  2. Create a sender profile with purpose LEAD_VERIFICATION.
  3. Wait until the sender profile and identity are READY.
  4. Create an ACTIVE email template.
  5. Enable verification on a LEAD_CAPTURE campaign with senderId, templateId, and optional ttlMinutes.

Reply YES Template Contract

Reply YES templates are regular 10x email templates sent through SES. Do not create SES-native templates.

Required body variables:

VariableMeaning
{{replyKeyword}}The keyword the visitor must reply with, currently YES
{{expiresInMinutes}}Verification expiry window

Supported variables:

VariableMeaning
{{campaignId}}Campaign id
{{formId}}Submitted form id
{{brandName}}Handle display name
{{pageUrl}}Page where the form was submitted
{{leadEmailMasked}}Masked visitor email

Example text body:

Reply {{replyKeyword}} to this email within {{expiresInMinutes}} minutes to confirm your request.

Campaign: {{campaignId}}
Page: {{pageUrl}}

Platform Reply Domain

Reply YES uses a platform-managed reply domain such as reply.10x.in or a stage-specific equivalent. Each pending lead receives a tokenized Reply-To address like:

verify+<token>@reply.10x.in

The token maps the inbound SES reply back to the pending lead. The submitted lead is only finalized when the reply contains a clear affirmative first line such as YES, YES., YES!, YES please, or Y.