Channel Alignment Playbook
Connect supported website, advertising, email, listing, and print placements to SMS entry points. Use campaign naming, source fields, and verified integrations to compare visits, conversations, and recorded outcomes.
The PlayAdd an SMS entry point where the channel supports the destination and message purpose.
Why It WorksConsistent names and tested source fields help connect campaign activity with conversations.
Best ForAgencies and marketers who need unified, channel-by-channel client reporting.
SMS Integration by Channel
| Channel | Integration Method | SmartLink Placement |
|---|---|---|
| Paid Search (Google) | Landing-page SMS CTA, or a direct destination where the ad platform permits it | “Text for a quote” button above the form |
| Meta (Facebook/Instagram) | Supported profile link or landing-page SMS CTA | “Send a text” CTA button |
| SEO / Website | SmartLink as “Text Us” button | Header, hero section, contact page |
| Google Business Profile | Supported website or contact destination | A linked page with a clear SMS option; verify what the listing permits |
| SmartLink button in email template | “Reply via text instead” CTA | |
| Direct Mail | QR code on printed piece | Front of mailer, large, with clear CTA |
Naming Convention That Makes Attribution Work
Name each entry point to identify the channel, campaign, and date, such as [Channel] | [Campaign] | [Date]. Use separate links or QR codes for the source distinctions you need. Naming alone does not create an analytics integration. Test which source fields, UTM values, and conversation identifiers are retained in TextingOnly and your connected systems.
Unified Client Reporting Framework
- Conversation starts by source: Count contacts who sent the initial message. Report marketing permission separately from an inquiry or offer request.
- Workflow progress by source: Compare starts, completed flows, and partial journeys using the same period and definitions.
- Cost per recorded outcome: Divide the matching campaign spend by the defined result, such as an inquiry or completed flow. Use the same attribution window.
- Business outcomes: Connect conversation identifiers with qualified opportunities or recorded sales in your existing system. A click, delivered SMS, or completed question flow is not a sale.
Frequently Asked Questions
Use a supported link or landing-page CTA for digital placements and a tested QR code for print. Check the channel’s current destination rules, then test desktop and mobile paths.
Consistent names help identify sources. Retained source fields, event configuration, and connected-system identifiers determine which activity can be attributed. Verify them with a test journey.
Compare visits, messages sent, replies, workflow progress, and outcomes recorded in connected systems. Keep delivery, reading, inquiries, permission, and sales separate. Report only events you have verified.