diff --git a/_analytics-reporting-attribution/campaign-reporting.md b/_analytics-reporting-attribution/campaign-reporting.md index 49917c0..065e508 100644 --- a/_analytics-reporting-attribution/campaign-reporting.md +++ b/_analytics-reporting-attribution/campaign-reporting.md @@ -3,10 +3,10 @@ languages: ["en", "es"] en: title: Campaign reporting - description: Learn how to read delivery, engagement, conversion, and attributed-revenue metrics for a delivered campaign. + description: Learn how to read a campaign's summary, delivery funnel, message performance, conversions, and attributed revenue. es: title: Reportes de campaña - description: Aprende a interpretar las métricas de entrega, interacción, conversión e ingresos atribuidos de una campaña entregada. + description: Aprende a interpretar el resumen, el embudo de entrega, el rendimiento de los mensajes, las conversiones y los ingresos atribuidos de una campaña. permalink: campaign-reporting permalink_es: reportes-de-campaña diff --git a/_campaigns/campaign-best-practices.md b/_campaigns/campaign-best-practices.md new file mode 100644 index 0000000..db01871 --- /dev/null +++ b/_campaigns/campaign-best-practices.md @@ -0,0 +1,19 @@ +--- +languages: ["en", "es"] + +en: + title: Campaign best practices + description: Make better decisions about campaign goals, audiences, channels, content, timing, testing, and measurement. +es: + title: Buenas prácticas para campañas + description: Toma mejores decisiones sobre objetivos, audiencias, canales, contenido, horarios, pruebas y medición. + +permalink: campaign-best-practices +permalink_es: buenas-practicas-campanas + +layout: guide +topic: campaigns +popular: false +--- + +{% translate_file campaigns/campaign-best-practices.md %} diff --git a/_campaigns/campaigns-overview.md b/_campaigns/campaigns-overview.md index dd5709f..bca32db 100644 --- a/_campaigns/campaigns-overview.md +++ b/_campaigns/campaigns-overview.md @@ -2,11 +2,11 @@ languages: ["en", "es"] en: - title: Campaigns and broadcasts overview - description: Understand when to send a one-time campaign and what to check before launch. + title: Campaigns overview + description: Understand the campaign lifecycle and when to use campaigns instead of playbooks or routes. es: - title: Resumen de campañas y broadcasts - description: Entiende cuándo enviar una campaña puntual y qué revisar antes de lanzarla. + title: Resumen de campañas + description: Entiende el ciclo de las campañas y cuándo usarlas en lugar de playbooks o rutas. permalink: campaigns-broadcasts-overview permalink_es: resumen-campanas-broadcasts diff --git a/_campaigns/creating-a-campaign.md b/_campaigns/creating-a-campaign.md index 1ea363f..63fadd5 100644 --- a/_campaigns/creating-a-campaign.md +++ b/_campaigns/creating-a-campaign.md @@ -3,10 +3,10 @@ languages: ["en", "es"] en: title: Create a campaign - description: Build, target, review, and send a campaign to your audience. + description: Choose channels and audiences, compose and test the message, then review, schedule, and send a campaign. es: title: Crea una campaña - description: Crea, segmenta, revisa y envía una campaña a tu audiencia. + description: Elige canales y audiencias, redacta y prueba el mensaje, y luego revisa, programa y envía una campaña. permalink: creating-a-campaign permalink_es: crear-una-campaña diff --git a/_config.yml b/_config.yml index e5c6202..b18c8d9 100644 --- a/_config.yml +++ b/_config.yml @@ -71,6 +71,7 @@ collections: order: - campaigns-overview.md - creating-a-campaign.md + - campaign-best-practices.md output: true audience: order: diff --git a/_i18n/en.yml b/_i18n/en.yml index 772f758..3aec6e2 100644 --- a/_i18n/en.yml +++ b/_i18n/en.yml @@ -12,7 +12,7 @@ getting-started: title: Start Here description: Launch Hellotext in the right order, from setup to your first useful sends. campaigns: - title: Campaigns & Broadcasts + title: Campaigns description: Plan, send, and measure one-time messages to selected audiences. audience: title: Audience & Segmentation diff --git a/_i18n/en/analytics-reporting-attribution/analytics-overview.md b/_i18n/en/analytics-reporting-attribution/analytics-overview.md index 4e3934b..a9ae1b5 100644 --- a/_i18n/en/analytics-reporting-attribution/analytics-overview.md +++ b/_i18n/en/analytics-reporting-attribution/analytics-overview.md @@ -6,11 +6,11 @@ This section connects three related questions: - Which customer actions happened after the message? - Which revenue was attributed to Hellotext? -## Campaign and broadcast reports +## Campaign reports Campaign reports help you review delivery, engagement, clicks, conversions, replies, and attributed revenue for a one-time send. -Use campaign reporting when you need to evaluate a broadcast, compare message performance, or decide what to improve before the next campaign. +Use campaign reporting when you need to evaluate a campaign, compare message performance, or decide what to improve before the next campaign. Keep reading: [Campaign reporting]({% link _analytics-reporting-attribution/campaign-reporting.md %}). diff --git a/_i18n/en/analytics-reporting-attribution/campaign-reporting.md b/_i18n/en/analytics-reporting-attribution/campaign-reporting.md index 9bb848c..2cb8f04 100644 --- a/_i18n/en/analytics-reporting-attribution/campaign-reporting.md +++ b/_i18n/en/analytics-reporting-attribution/campaign-reporting.md @@ -1,49 +1,95 @@ -Campaign reports show delivery, engagement, attributed purchases, and attributed revenue for a delivered campaign. Use them to compare messages and channels, inspect customer activity, and understand which orders were linked to the campaign under Hellotext's attribution methodology. +Campaign reports are generated automatically after delivery. They bring together message delivery, tracked engagement, attributed purchases, and attributed revenue so you can understand both what happened and what to improve next. -To open a report, go to **Campaigns** and select a delivered campaign. Reports are available after a campaign has been delivered. +To open one, go to **Campaigns**, open the delivered campaigns view, and select a campaign. -## Select the report period +## Choose the reporting period -The report opens with the **First 14 days** preset. You can change the date range to inspect a different period. +The report opens with **First 14 days** selected. You can switch to the first 7 or 30 days, or choose a custom range. -The report period controls which activity appears in the report. It does not extend the attribution window used to decide whether an order belongs to the campaign. +The selected period updates the metrics, chart, funnel, message results, revenue breakdowns, and recent activity together. It filters when those results were recorded; it does not change the attribution window used to decide whether a purchase belongs to the campaign. -## Read the main metrics +A campaign message can remain listed even when its results fall outside the selected range. In that case, its row can show zero values until you choose a period that includes its activity. -* **Revenue:** active revenue attributed to the campaign during the selected report period. -* **ROI:** attributed campaign revenue divided by the estimated cost of delivering its messages. -* **Conversion:** attributed purchase count divided by delivered messages. -* **Revenue/msg:** attributed campaign revenue divided by delivered messages. +## Read the campaign summary + +The four summary cards answer different questions: + +* **Attributed revenue:** how much revenue came from purchases attributed to this campaign during the selected period. +* **Average ROI:** attributed revenue divided by the estimated cost of delivering the campaign messages. +* **Conversion:** attributed purchases divided by delivered messages. +* **Revenue/message:** attributed revenue divided by delivered messages. + +Select a card to update the chart and see how that metric changed over time. Conversion is based on attributed purchases and delivered messages; it is not the percentage of people who clicked and then purchased. + +## Follow the delivery funnel + +The **Campaign delivery funnel** moves through four stages: + +* **Sent:** campaign messages dispatched during the selected period. +* **Delivered:** messages that reached customers. +* **Engaged:** delivered messages that produced at least one tracked link click during the period. This is a count of engaged messages, not the total number of clicks. +* **Conversion:** purchases attributed to the campaign. Its percentage uses attributed purchases divided by delivered messages, matching the summary conversion metric. + +Use the funnel to find where performance changes. A large difference between sent and delivered points to delivery or contactability. Strong delivery with little engagement points more toward the audience, message, or call to action. + +## Compare campaign messages + +The **Messages** section shows the date and preview of each campaign message, followed by: + +* **Delivered:** messages successfully delivered. * **CTR:** tracked clicks divided by delivered messages. +* **Average ROI:** attributed revenue divided by estimated delivery cost. +* **Conversion:** attributed purchases divided by delivered messages. +* **Revenue/message:** attributed revenue divided by delivered messages. +* **Revenue:** revenue attributed to that message. + +This lets you compare the actual messages without mixing click performance with purchase performance. A message can have a healthy CTR but a weaker conversion rate if customers click without completing a purchase. + +## Understand time to conversion + +**Time to conversion** shows how long it took attributed sales to happen after the campaign launched, using ranges such as the same day, 1–3 days, 4–7 days, and later periods. + +The report period filters when the attributed sale was recorded. A sale can therefore appear days after message delivery while still belonging to the campaign under the applicable attribution rules. + +## Compare revenue by channel and segment + +**Attributed revenue by channel** shows how attributed revenue is distributed across the available messaging channels. Use it to see which channel contributed more revenue, not just which one delivered more messages. + +**Attributed revenue by segment** shows the distribution across customer segments when segment data is available. Treat small samples carefully before applying the result to a future audience. -Conversion is not the percentage of unique clicks that purchased. It uses attributed purchases and delivered messages. +## Review recent activity -## Compare delivery and broadcasts +**Recent activity** lists tracked customer events associated with the campaign during the selected period. You can search for a customer or activity and open an event to inspect more detail. -The delivery funnel shows how messages progressed through delivery and engagement. When a campaign has more than one broadcast or channel, the broadcast table helps you compare delivered messages, CTR, ROI, conversion, revenue per message, and attributed revenue. +An event appearing here does not automatically mean it generated attributed revenue. The purchase still needs eligible customer, order, source, and timing evidence. -## How clicks and deliveries support attribution +## Separate campaign activity from attribution -A tracked short-link click is active campaign evidence and normally opens a seven-day attribution window from the eligible click. A click is not the only campaign evidence: an eligible campaign delivery can provide passive evidence within the default 24-hour window. +A tracked short-link click is active campaign evidence and normally opens a seven-day attribution window from the eligible click. A click is not the only possible evidence: an eligible campaign delivery can provide passive evidence within the default 24-hour window. -Hellotext evaluates available source evidence and its precedence before assigning the order. A recognized external marketing source can take precedence over Hellotext evidence. Read [How we attribute sales]({% link _analytics-reporting-attribution/sales-attribution.md %}) for the complete methodology. +Hellotext evaluates the available evidence and its precedence before assigning a purchase. A recognized external marketing source can take precedence over Hellotext evidence. Read [How we attribute sales]({% link _analytics-reporting-attribution/sales-attribution.md %}) for the complete methodology. -## Explore revenue and activity +## Turn the report into a decision -Depending on the campaign and available data, the report can also include: +* **Sent is much higher than delivered:** review consent, reachable customer profiles, channel availability, and delivery problems. +* **Delivery is healthy but CTR is low:** review audience relevance, message clarity, and the call to action. +* **CTR is healthy but conversion is low:** review the destination, product availability, offer, and checkout experience. +* **Revenue is present but ROI or revenue/message is weak:** compare delivery cost, channel mix, and audience quality. +* **One channel or segment contributes more revenue:** use it as a signal for the next campaign, while accounting for audience size and message volume. +* **Conversions arrive over several days:** wait long enough before treating the first day's result as final. -* Time to conversion -* Revenue by channel -* Revenue by segment -* Delivery and engagement events -* Purchases and other tracked customer events +## When results are missing or unexpected -An event appearing in campaign activity does not automatically mean that it created attributed revenue. The event still needs eligible customer, order, source, and timing evidence. +First confirm that the selected period includes the campaign activity. Then verify that tracked links and purchase events are available. Supported commerce integrations can send purchase data automatically; custom storefronts can use [Hellotext.js or the API]({% link _developers/tracking-events.md %}). -Supported commerce integrations can send purchase data automatically. For custom storefronts and events, use [Hellotext.js or the API]({% link _developers/tracking-events.md %}). +If activity is still missing, follow [Troubleshoot missing signals or activity]({% link _troubleshooting-deliverability/troubleshoot-missing-signals-or-activity.md %}). ## Related guides +* [Create a campaign]({% link _campaigns/creating-a-campaign.md %}) +* [Campaign best practices]({% link _campaigns/campaign-best-practices.md %}) +* [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) * [Tracking links in campaigns and journeys]({% link _developers/tracking-on-campaigns-and-journeys.md %}) * [Using tracked links]({% link _analytics-reporting-attribution/tracked-links.md %}) +* [How we attribute sales]({% link _analytics-reporting-attribution/sales-attribution.md %}) * [Analytics overview]({% link _analytics-reporting-attribution/analytics-overview.md %}) diff --git a/_i18n/en/analytics-reporting-attribution/tracked-links.md b/_i18n/en/analytics-reporting-attribution/tracked-links.md index 6a81a86..cbd8102 100644 --- a/_i18n/en/analytics-reporting-attribution/tracked-links.md +++ b/_i18n/en/analytics-reporting-attribution/tracked-links.md @@ -14,3 +14,9 @@ You can look at our client-side button at the right of the dropdown. +Select **Next** to continue. Give the campaign a clear internal name in the header so teammates can recognize it later in Draft, Scheduled, Delivered, and reporting views. -The aggregated total of recipients to reach will be visible on the right side of the page. +## 2. Choose who will receive it -Learn more: **[Lists and Segments]({% link _audience/lists-and-segments.md %})**. +The audience step starts with **All audience**. You can keep it when every eligible customer profile should be considered, or replace it with a more focused selection. -### Excluding audiences +You can include or exclude: -It is possible to exclude certain audiences by selecting them first and then clicking on the *Include* label. +- Lists. +- Segments. +- Audiences from previously scheduled or delivered campaigns. -For an audience to remain excluded, its label should say *Exclude*. +Use the add button to combine multiple audience rules. Change **Include** to **Exclude** when a group should be removed from the campaign. -## Composing your message +Hellotext deduplicates overlapping groups and updates the estimated target automatically. The estimate considers the selected channels, subscription state, contactability, inclusions, and exclusions, so it can be smaller than the total size of the selected lists or segments. -Take your time to write a clear message. Imagine yourself as the recipient. How would you feel receiving this message? +Use the settings control beside **Estimated target** when you want to limit the campaign to a maximum number of eligible customers from the selected audience. This limit does not make an ineligible profile contactable. -Typically, short and effective messages work better than longer ones. +Keep reading: [Lists vs. segments]({% link _audience/lists-and-segments.md %}). -If your campaign uses SMS, keep SMS length in mind. SMS messages have a limit of 160 characters. If you include characters that are not originally supported in the GSM-7 specification, such as accents and emojis, an encoding conversion to UCS-2 will be done and the total length per SMS message will be reduced to 80 characters. +## 3. Compose the message -If your SMS message exceeds this limit, it will require an additional SMS. Whenever possible, Hellotext tries to merge different SMS into one message, and when this is not possible the message will be sent in separate SMS messages. +Write one focused message with a clear next action. The editor shows a channel preview while you compose. -A counter with the remaining SMS characters and the number of SMS messages this campaign will consume per recipient is available in the compose area when SMS applies. +Available tools depend on the delivery option. A campaign can include: -A preview of the message is available on the right side of the page. It can help give you an idea of how the message could look when it is split into different SMS. +- Formatted text supported by the selected channel. +- A tracked link. +- Personalization tags from customer profile properties. +- A coupon. +- A sending channel or sender. +- WhatsApp content such as an attachment, location, footer, or buttons when supported. -### Add a shortened link +When WhatsApp is part of the campaign, the message is also prepared as a WhatsApp template. New or changed WhatsApp template content may need Meta approval before it can be delivered. -This feature creates a shorter version of any URL in a simple format that looks like *hello.link/abcdef*. +Keep reading: [Message editor overview]({% link _numbers/message-editor-overview.md %}). -We always recommend using this tool to shorten the URL that will take visitors to your site, promotion, or a product. +## Add tracked links -The benefits of shortening links are two-fold: it keeps your message shorter, leaving more characters for the actual message. +Use the editor's link tool instead of pasting a long destination URL. Hellotext creates a short `hello.link` URL, records eligible clicks, and connects the visit with later tracked activity. -It also tracks which recipients clicked the short link and can connect later purchases or other events with that session. +A tracked click can contribute active evidence for campaign attribution, but it is not the only evidence Hellotext evaluates. -Supported commerce integrations can send purchase data automatically. For a custom storefront or custom events, install *Hellotext.js* or use the API to process the session and track events. +Keep reading: [Tracked links]({% link _analytics-reporting-attribution/tracked-links.md %}). -A tracked click is useful active attribution evidence, but it is not the only evidence Hellotext can use. Read [How we attribute sales]({% link _analytics-reporting-attribution/sales-attribution.md %}) for the complete methodology. +## Add personalization tags -### Add tags +Tags insert customer profile properties into the delivered message. Use a fallback when the property may be missing, for example `{name|customer}`. -Make your messages more personal by referencing customer profile properties. For example, display the profile's name using the tag _{name}_. The delivered message will replace the tag with the customer profile's name. +Check the preview carefully when using tags. The fallback should produce a natural sentence for customer profiles without that value. -You can find tags for all your customer profile properties such as: +Keep reading: [Personalization tags]({% link _audience/personalization-tags.md %}). -* *{name}* -* *{last_name}* -* *{phone}* -* *{birthdate}* -* Any custom properties also have a matching tag following the same tag naming convention: For example, if the property is called _My Property_ a tag to reference this property will be automatically available with the name _{my_property}_ +## Add a coupon -### Setting a default value +Use the coupon tool to reference a coupon already available in Hellotext. This keeps the coupon connected to the campaign and its results instead of treating a manually typed code as plain text. -Not every customer profile is likely to have the property you want to use in a tag. For example, not every campaign recipient may have a name. Depending on how you craft your message, this can make the message read oddly if no value is shown. +Confirm that the coupon rules, expiration, and eligible products match the selected audience before sending. -To solve this, you can pass a default value inside your tag separated by the pipe like _{name|customer}_. +## 4. Preview and send a test -If your message is for example: +Use the preview to check the message in every selected channel. Review: -* *Dear **{name|customer}**, we have a special offer...* +- The first line and call to action. +- Personalization and fallback values. +- Tracked-link destinations. +- Coupon text and validity. +- WhatsApp attachments, buttons, footer, or location. +- SMS length and the message-part estimate shown by the editor. -For a recipient without a name, it will be sent as: +Send a test to a phone number before continuing. An SMS test can be delivered directly. A WhatsApp test with new template content can remain scheduled until Meta approves that template. -* *Dear **customer**, we have a special offer...* +A test confirms presentation and delivery to the test number. It does not prove that every customer profile in the final audience is eligible. -### Add coupons +## 5. Choose when it will be sent -You can reference coupons already created. Referencing coupons instead of manually writing them gives you powerful reporting and better insights and understanding of the impact they had on your campaign results. +Choose one of these options: -### Choose channel and sender +- **Send now:** starts the approval and delivery process immediately. +- **Send later:** selects a future date and time. -Choose the channel and sender that match the audience and campaign goal. +Hellotext applies the communication windows required for the destination country and the business's night-hour settings. If the selected time is not allowed, the interface can require another time or move delivery to the next allowed window. -For SMS campaigns, make sure your account has an active sender or short code available before launching. +Use **Save & Close** at any step when you want to keep the campaign as a draft and finish it later. -For WhatsApp campaigns, make sure your WhatsApp account is connected and ready before sending. +## 6. Review and confirm -Keep reading: **[Messaging channels overview]({% link _numbers/messaging-overview.md %})**. +Before selecting **Send**, verify: -## Schedule and deliver +- The estimated number of targeted customers. +- Included and excluded audiences. +- Delivery channels and sender. +- Message preview for every channel. +- Tracked links, tags, coupon, and WhatsApp content. +- Delivery date and time. +- Estimated Meta cost when WhatsApp applies. -You can send your campaign right away or schedule it to send in the future on a particular day and time. +The confirmation screen is the last opportunity to catch a wrong audience or message before the campaign enters approval and delivery. -### Editorial review +## Understand campaign review -Please keep in mind that if your campaign targets more than 100 recipients it will be subject to a quick editorial review before it is delivered. +Campaigns targeting at least 100 customers require editorial review. A WhatsApp campaign can also wait for Meta when its template has not already been approved. -During business hours this is fairly quick and usually takes less than 10 minutes. +While review is pending, the campaign appears **In review** or **WhatsApp in review**. Once approved, it follows the selected delivery time. If a reviewer or Meta rejects the content, open the campaign, review the feedback, make the requested changes, and submit it again. -Once a campaign is approved, it will continue its course to delivery. You do not need to do anything on your part during the approval process unless there is a request to adjust the campaign, in which case after a new change is made it will be marked for review again. +Approval time can vary, especially when Meta must review new WhatsApp content. Leave enough time before a scheduled promotion or event. + +## After sending + +Use the Campaigns tabs to follow the campaign: + +- **Draft:** saved but not submitted. +- **Scheduled:** submitted, in review, approved for a future time, or preparing to send. +- **Delivered:** delivery has started and results are available. +- **Archived:** completed campaigns moved out of the active Delivered list. + +Replies from customers continue into the Inbox through the corresponding channel. Campaign reports are generated automatically after delivery so you can review delivered messages, engagement, conversion, ROI, and attributed revenue. + +Keep reading: [Campaign reporting]({% link _analytics-reporting-attribution/campaign-reporting.md %}). + +## Preflight checklist + +Before the final send, confirm that: + +- The goal requires a one-time campaign rather than a playbook or route. +- The audience is focused and has channel-specific consent. +- Exclusions remove internal, test, invalid, or inappropriate customer profiles. +- The sender and fallback behavior are correct. +- The message has one clear next action. +- Links, tags, coupons, media, and buttons work in a test. +- The send time leaves room for editorial or Meta review. +- Someone will monitor replies, delivery issues, and results after launch. + +## Related guides + +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaign best practices]({% link _campaigns/campaign-best-practices.md %}) +- [Who can I message?]({% link _audience/consent-and-subscriber-status.md %}) +- [Messaging channels overview]({% link _numbers/messaging-overview.md %}) +- [Message editor overview]({% link _numbers/message-editor-overview.md %}) +- [Campaign reporting]({% link _analytics-reporting-attribution/campaign-reporting.md %}) +- [How Hellotext works]({% link _getting-started/how-hellotext-works.md %}) diff --git a/_i18n/en/getting-started/frequent-questions.md b/_i18n/en/getting-started/frequent-questions.md index 60f096f..109c811 100644 --- a/_i18n/en/getting-started/frequent-questions.md +++ b/_i18n/en/getting-started/frequent-questions.md @@ -78,7 +78,7 @@ Keep reading: [Capture tools overview]({% link _captures/capture-overview.md %}) ## What is the difference between a campaign and a playbook? -A campaign is a one-time message to a selected audience. Use campaigns for announcements, promotions, and focused broadcasts. +A campaign is a one-time message to a selected audience. Use campaigns for announcements, promotions, and other focused sends. A playbook is a repeatable system trained for a business mission, such as recovering carts, driving repeat purchases, reactivating customers, collecting reviews, or handling support. @@ -87,7 +87,7 @@ Unlike a fixed flow, a playbook can use signals to decide what to do for each cu Keep reading: - [How Hellotext works: playbooks, campaigns, and Inbox]({% link _getting-started/how-hellotext-works.md %}) -- [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) - [Playbooks and automation overview]({% link _journeys/playbooks-overview.md %}) ## How should I prepare my first send? diff --git a/_i18n/en/getting-started/go-live-checklist.md b/_i18n/en/getting-started/go-live-checklist.md index 15beed9..c00098c 100644 --- a/_i18n/en/getting-started/go-live-checklist.md +++ b/_i18n/en/getting-started/go-live-checklist.md @@ -119,7 +119,7 @@ Pausing early is better than letting a preventable issue reach more customers. - [Verify your data and signals after setup]({% link _integrations/verify-data-and-signals.md %}) - [Messaging channels overview]({% link _numbers/messaging-overview.md %}) - [Capture tools overview]({% link _captures/capture-overview.md %}) -- [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) - [Inbox and conversations overview]({% link _team/inbox-overview.md %}) - [AI handoff to Inbox]({% link _team/ai-handoff-to-inbox.md %}) - [SMS sending limits for new businesses]({% link _troubleshooting-deliverability/sms-sending-limits-for-new-businesses.md %}) diff --git a/_i18n/en/getting-started/how-hellotext-works.md b/_i18n/en/getting-started/how-hellotext-works.md index 92d845b..fec8563 100644 --- a/_i18n/en/getting-started/how-hellotext-works.md +++ b/_i18n/en/getting-started/how-hellotext-works.md @@ -49,7 +49,7 @@ Campaigns are best for: - Product launches. - Restocks. - Event reminders. -- Seasonal or time-bound broadcasts. +- Seasonal or time-bound campaigns. Campaigns are useful when the same message should reach a selected audience once. If the message should react to each customer's behavior over time, use a playbook instead. @@ -112,7 +112,7 @@ If you are unsure, start smaller. Choose one goal, one channel, one audience, an - [First wins starter pack]({% link _getting-started/first-wins-starter-pack.md %}) - [What are signals?]({% link _journeys/what-are-signals.md %}) - [Playbooks and automation overview]({% link _journeys/playbooks-overview.md %}) -- [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) - [Inbox and conversations overview]({% link _team/inbox-overview.md %}) - [AI handoff to Inbox]({% link _team/ai-handoff-to-inbox.md %}) - [Choose your first playbook]({% link _journeys/choose-your-first-playbook.md %}) diff --git a/_i18n/en/getting-started/what-is-hellotext.md b/_i18n/en/getting-started/what-is-hellotext.md index a45b399..69fa622 100644 --- a/_i18n/en/getting-started/what-is-hellotext.md +++ b/_i18n/en/getting-started/what-is-hellotext.md @@ -60,9 +60,9 @@ Capture tools help customers subscribe, start conversations, or share informatio Captures usually feed the customer profile and can start a welcome message, route, or playbook. -### Campaigns and broadcasts +### Campaigns -Campaigns are one-time sends to a selected audience. Use them for announcements, launches, promotions, or planned broadcasts. +Campaigns are one-time sends to a selected audience. Use them for announcements, launches, promotions, or other planned messages. Campaigns still matter, but they are not the center of Hellotext. Playbooks and Inbox workflows help Hellotext respond continuously to customer behavior. diff --git a/_i18n/en/journeys/anniversary-surprise-playbook.md b/_i18n/en/journeys/anniversary-surprise-playbook.md index 0d6f844..690a849 100644 --- a/_i18n/en/journeys/anniversary-surprise-playbook.md +++ b/_i18n/en/journeys/anniversary-surprise-playbook.md @@ -33,7 +33,7 @@ It is a good fit when: - The business wants to offer a greeting or approved coupon without creating manual campaigns. - Your team wants a retention moment that does not depend on inactivity, cart behavior, or birthday. -For personal birthdays, use [Birthday Bash]({% link _journeys/birthday-bash-playbook.md %}). For customers who have gone quiet, use [Soft Reactivation]({% link _journeys/soft-reactivation-playbook.md %}), [Dormant Revival]({% link _journeys/dormant-revival-playbook.md %}), or [Sunset Saver]({% link _journeys/sunset-saver-playbook.md %}) depending on the inactivity window. For commercial dates such as holidays, launches, or one-time promotions, use [Campaigns and broadcasts]({% link _campaigns/campaigns-overview.md %}). +For personal birthdays, use [Birthday Bash]({% link _journeys/birthday-bash-playbook.md %}). For customers who have gone quiet, use [Soft Reactivation]({% link _journeys/soft-reactivation-playbook.md %}), [Dormant Revival]({% link _journeys/dormant-revival-playbook.md %}), or [Sunset Saver]({% link _journeys/sunset-saver-playbook.md %}) depending on the inactivity window. For commercial dates such as holidays, launches, or one-time promotions, use [Campaigns]({% link _campaigns/campaigns-overview.md %}). ## What it needs before launch @@ -101,7 +101,7 @@ Use the type of date or signal to decide which playbook should act. | Customer is starting to go quiet | [Soft Reactivation]({% link _journeys/soft-reactivation-playbook.md %}) | | Customer has been inactive for around 3 months | [Dormant Revival]({% link _journeys/dormant-revival-playbook.md %}) | | Customer has been inactive or not reactivated for around 12 months | [Sunset Saver]({% link _journeys/sunset-saver-playbook.md %}) | -| You have a commercial date or one-time launch | [Campaigns and broadcasts]({% link _campaigns/campaigns-overview.md %}) | +| You have a commercial date or one-time launch | [Campaigns]({% link _campaigns/campaigns-overview.md %}) | Anniversary Surprise can coexist with other playbooks when each one responds to a different moment. Still, avoid sending several promotional messages to the same customer at the same moment if another active playbook is a better fit. diff --git a/_i18n/en/journeys/back-in-stock-pounce.md b/_i18n/en/journeys/back-in-stock-pounce.md index bf29c36..822c882 100644 --- a/_i18n/en/journeys/back-in-stock-pounce.md +++ b/_i18n/en/journeys/back-in-stock-pounce.md @@ -79,7 +79,7 @@ Use the customer signal to decide the owner. | Customer viewed an available product but did not add to cart | [Browse Recovery]({% link _journeys/browse-recovery-playbook.md %}) | | Customer added products to cart or checkout and left | [AI Cart Saver]({% link _journeys/ai-cart-saver-playbook.md %}) or [Cart Saver route]({% link _journeys/cart-saver-route.md %}) | | Customer needs help choosing a product or alternative | [Smart Recommender]({% link _journeys/smart-recommender-playbook.md %}) | -| Business wants to announce a restock to a selected audience once | Campaign or broadcast | +| Business wants to announce a restock to a selected audience once | Campaign | Back-in-Stock Pounce can run alongside browse and cart recovery when the ownership is clear. Back-in-stock handles the unavailable-item moment; browse and cart recovery handle available products that the customer did not buy. @@ -154,5 +154,5 @@ Tune one thing at a time among the cards the playbook exposes: product scope, ch - [AI Cart Saver playbook]({% link _journeys/ai-cart-saver-playbook.md %}) - [Cart Saver route]({% link _journeys/cart-saver-route.md %}) - [Smart Recommender playbook]({% link _journeys/smart-recommender-playbook.md %}) -- [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) - [Playbook reporting]({% link _analytics-reporting-attribution/playbook-reporting.md %}) diff --git a/_i18n/en/journeys/birthday-bash-playbook.md b/_i18n/en/journeys/birthday-bash-playbook.md index 80d20cf..4c55920 100644 --- a/_i18n/en/journeys/birthday-bash-playbook.md +++ b/_i18n/en/journeys/birthday-bash-playbook.md @@ -99,7 +99,7 @@ Use the type of moment to decide which playbook should act. | Customer is starting to go quiet | [Soft Reactivation]({% link _journeys/soft-reactivation-playbook.md %}) | | Customer has been inactive for around 3 months | [Dormant Revival]({% link _journeys/dormant-revival-playbook.md %}) | | Customer has been inactive or not reactivated for around 12 months | [Sunset Saver]({% link _journeys/sunset-saver-playbook.md %}) | -| You want to send a commercial date announcement | [Campaigns and broadcasts]({% link _campaigns/campaigns-overview.md %}) | +| You want to send a commercial date announcement | [Campaigns]({% link _campaigns/campaigns-overview.md %}) | Birthday Bash can coexist with other playbooks because its signal is a profile date. Still, avoid sending several promotional messages to the same customer at the same moment if another active playbook is a better fit. diff --git a/_i18n/en/journeys/choose-your-first-playbook.md b/_i18n/en/journeys/choose-your-first-playbook.md index d667aa6..da0ccf7 100644 --- a/_i18n/en/journeys/choose-your-first-playbook.md +++ b/_i18n/en/journeys/choose-your-first-playbook.md @@ -38,7 +38,7 @@ After you choose the first option to launch, follow [How to enable a playbook]({ | Measure loyalty after delivery | [NPS Pulse]({% link _journeys/nps-pulse-playbook.md %}) | Use this when delivered-order signals are reliable and you want a relationship-level 0-10 recommendation signal. | | Answer frequent questions or reduce support load | [Instant Answers]({% link _journeys/instant-answers-playbook.md %}), [Order-Update Delight]({% link _journeys/order-update-playbook.md %}), [Return & Exchange Helper]({% link _journeys/return-and-exchange-helper-playbook.md %}), or [Order Cancellation Assistant]({% link _journeys/order-cancellation-assistant-playbook.md %}) | Start here when your team spends time answering repeat questions and you have clear policies, order data, and handoff rules. | | Measure satisfaction after resolved conversations | [CSAT Pulse]({% link _journeys/csat-pulse-playbook.md %}) | Use this when support, Inbox, AI, or playbook conversations can be resolved and negative feedback should create follow-up. | -| Send one planned announcement | A campaign or broadcast | Use a campaign when the message is time-bound and should go to a selected audience once. | +| Send one planned announcement | A campaign | Use a campaign when the message is time-bound and should go to a selected audience once. | | Build a custom flow | A journey route or [custom agent]({% link _journeys/custom-agent-playbook.md %}) | Use this when no prebuilt mission fits, or when you need specific steps, conditions, actions, or business logic. | ## Start small @@ -118,6 +118,6 @@ Then adjust one thing at a time among the controls that option actually exposes, - [Abandoned cart: route template vs AI playbook]({% link _journeys/abandoned-cart-route-vs-ai-playbook.md %}) - [Getting started with journeys]({% link _journeys/getting-started-with-journeys.md %}) - [Capture tools overview]({% link _captures/capture-overview.md %}) -- [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) - [Playbook reporting]({% link _analytics-reporting-attribution/playbook-reporting.md %}) - [Analytics, reporting, and attribution overview]({% link _analytics-reporting-attribution/analytics-overview.md %}) diff --git a/_i18n/en/journeys/dormant-revival-playbook.md b/_i18n/en/journeys/dormant-revival-playbook.md index 4ce62ad..e009f0b 100644 --- a/_i18n/en/journeys/dormant-revival-playbook.md +++ b/_i18n/en/journeys/dormant-revival-playbook.md @@ -112,7 +112,7 @@ Use the customer moment to decide the owner. | Customer may need to reorder a consumable product | [Replenishment Driver]({% link _journeys/replenishment-driver-playbook.md %}) | | Customer recently bought and may want a related product | [Cross-Sell Driver]({% link _journeys/cross-sell-driver-playbook.md %}) | | Customer abandoned a cart or checkout | [AI Cart Saver]({% link _journeys/ai-cart-saver-playbook.md %}) or [Cart Saver route]({% link _journeys/cart-saver-route.md %}) | -| You want to send a planned one-time message to a selected audience | [Campaigns and broadcasts]({% link _campaigns/campaigns-overview.md %}) | +| You want to send a planned one-time message to a selected audience | [Campaigns]({% link _campaigns/campaigns-overview.md %}) | Dormant Revival can coexist with other playbooks when each one owns a different moment. It should not compete with a more specific signal, and it should stop trying to win back a customer who already returned, replied, opted out, or entered another active flow. diff --git a/_i18n/en/journeys/playbook-library-by-mission.md b/_i18n/en/journeys/playbook-library-by-mission.md index 75298ec..f48d05d 100644 --- a/_i18n/en/journeys/playbook-library-by-mission.md +++ b/_i18n/en/journeys/playbook-library-by-mission.md @@ -70,11 +70,11 @@ In this family, Hellotext also looks for the most cost-efficient available chann Start here when the message is tied to a launch, promotion, holiday, inventory moment, or one-time announcement. -These planned moments normally belong in Campaigns unless your account exposes a specific playbook for the job. Common workflows include seasonal promotions, product launches, inventory or clearance announcements, classic broadcasts, and AI-personalized broadcasts when that option is available in your account. +These planned moments normally belong in Campaigns unless your account exposes a specific playbook for the job. Common workflows include seasonal promotions, product launches, inventory or clearance announcements, scheduled campaigns, and AI-personalized campaigns when that option is available in your account. Use a campaign when the send should happen once to a selected audience. Use a playbook when the system should keep reacting to customer signals over time. -Keep reading: [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}). +Keep reading: [Campaigns overview]({% link _campaigns/campaigns-overview.md %}). ## Improve support and customer experience @@ -126,7 +126,7 @@ If you are unsure where to start, choose the mission that matches the first bott | Visitors browse but do not buy | [First-Purchase Driver]({% link _journeys/first-purchase-driver-playbook.md %}), [Browse Recovery]({% link _journeys/browse-recovery-playbook.md %}), [Complete-the-Look]({% link _journeys/complete-the-look-playbook.md %}), or [Smart Recommender]({% link _journeys/smart-recommender-playbook.md %}) | | Buyers do not return | [Replenishment Driver]({% link _journeys/replenishment-driver-playbook.md %}), [Cross-Sell Driver]({% link _journeys/cross-sell-driver-playbook.md %}), [Birthday Bash]({% link _journeys/birthday-bash-playbook.md %}), [Anniversary Surprise]({% link _journeys/anniversary-surprise-playbook.md %}), or [Soft Reactivation]({% link _journeys/soft-reactivation-playbook.md %}) | | Customers have gone cold | [Dormant Revival]({% link _journeys/dormant-revival-playbook.md %}) or [Sunset Saver]({% link _journeys/sunset-saver-playbook.md %}) | -| You have a timed announcement | A campaign or broadcast | +| You have a timed announcement | A campaign | | Support work is repetitive | [Instant Answers]({% link _journeys/instant-answers-playbook.md %}), [Order-Update Delight]({% link _journeys/order-update-playbook.md %}), [Return & Exchange Helper]({% link _journeys/return-and-exchange-helper-playbook.md %}), [Order Cancellation Assistant]({% link _journeys/order-cancellation-assistant-playbook.md %}), or [CSAT Pulse]({% link _journeys/csat-pulse-playbook.md %}) | | You need product reviews | [Review Builder]({% link _journeys/review-builder-playbook.md %}) | | You need loyalty feedback after delivery | [NPS Pulse]({% link _journeys/nps-pulse-playbook.md %}) | diff --git a/_i18n/en/journeys/price-drop-pouncer.md b/_i18n/en/journeys/price-drop-pouncer.md index 6b83c72..449d8fd 100644 --- a/_i18n/en/journeys/price-drop-pouncer.md +++ b/_i18n/en/journeys/price-drop-pouncer.md @@ -36,7 +36,7 @@ It is a good fit when: - Product links, images, prices, sellability, and availability are accurate. - You want an automatic price alert, not a broad sale campaign. -Use a campaign or broadcast when you want to announce a sale, promotion, or price change to a selected audience, even if those customers did not show interest in the specific product. +Use a campaign when you want to announce a sale, promotion, or price change to a selected audience, even if those customers did not show interest in the specific product. Use [Back-in-Stock Pounce]({% link _journeys/back-in-stock-pounce.md %}) when the key change is availability, not price. Use [Browse Recovery]({% link _journeys/browse-recovery-playbook.md %}) when the shopper viewed an available product but no price drop happened. Use [AI Cart Saver]({% link _journeys/ai-cart-saver-playbook.md %}) or [Cart Saver route]({% link _journeys/cart-saver-route.md %}) when the strongest signal is an abandoned cart or checkout. Use [Smart Recommender]({% link _journeys/smart-recommender-playbook.md %}) when the customer needs help finding a better product or alternative. @@ -121,7 +121,7 @@ Use the customer moment to decide the owner. | Shopper viewed an available product but no price drop happened | [Browse Recovery]({% link _journeys/browse-recovery-playbook.md %}) | | Shopper added products to cart or checkout and left | [AI Cart Saver]({% link _journeys/ai-cart-saver-playbook.md %}) or [Cart Saver route]({% link _journeys/cart-saver-route.md %}) | | Shopper needs a recommendation or alternative | [Smart Recommender]({% link _journeys/smart-recommender-playbook.md %}) | -| Business wants to announce a sale to a selected audience once | Campaign or broadcast | +| Business wants to announce a sale to a selected audience once | Campaign | Price-Drop Pouncer can run alongside browse, cart recovery, recommendations, and back-in-stock alerts when ownership is clear. Price-Drop Pouncer owns the moment when the new price is the reason to re-engage. @@ -201,5 +201,5 @@ Tune one thing at a time: channel, tone, assignment, product data, catalog sync, - [AI Cart Saver playbook]({% link _journeys/ai-cart-saver-playbook.md %}) - [Cart Saver route]({% link _journeys/cart-saver-route.md %}) - [Smart Recommender playbook]({% link _journeys/smart-recommender-playbook.md %}) -- [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}) +- [Campaigns overview]({% link _campaigns/campaigns-overview.md %}) - [Playbook reporting]({% link _analytics-reporting-attribution/playbook-reporting.md %}) diff --git a/_i18n/en/journeys/soft-reactivation-playbook.md b/_i18n/en/journeys/soft-reactivation-playbook.md index 387ca86..022137d 100644 --- a/_i18n/en/journeys/soft-reactivation-playbook.md +++ b/_i18n/en/journeys/soft-reactivation-playbook.md @@ -110,7 +110,7 @@ Use the customer moment to decide the owner. | Customer may need to reorder a consumable product | [Replenishment Driver]({% link _journeys/replenishment-driver-playbook.md %}) | | Customer recently bought and may want a related product | [Cross-Sell Driver]({% link _journeys/cross-sell-driver-playbook.md %}) | | Customer abandoned a cart or checkout | [AI Cart Saver]({% link _journeys/ai-cart-saver-playbook.md %}) or [Cart Saver route]({% link _journeys/cart-saver-route.md %}) | -| You want to send a planned one-time message to a selected audience | [Campaigns and broadcasts]({% link _campaigns/campaigns-overview.md %}) | +| You want to send a planned one-time message to a selected audience | [Campaigns]({% link _campaigns/campaigns-overview.md %}) | Soft Reactivation can coexist with other playbooks when each one owns a different moment. It should not compete with a more specific signal, such as an abandoned cart, an expected replenishment window, or an active support conversation. diff --git a/_i18n/en/journeys/sunset-saver-playbook.md b/_i18n/en/journeys/sunset-saver-playbook.md index 1bf38d7..b8f153d 100644 --- a/_i18n/en/journeys/sunset-saver-playbook.md +++ b/_i18n/en/journeys/sunset-saver-playbook.md @@ -114,7 +114,7 @@ Use the customer moment to decide the owner. | Customer may need to reorder a consumable product | [Replenishment Driver]({% link _journeys/replenishment-driver-playbook.md %}) | | Customer recently bought and may want a related product | [Cross-Sell Driver]({% link _journeys/cross-sell-driver-playbook.md %}) | | Customer abandoned a cart or checkout | [AI Cart Saver]({% link _journeys/ai-cart-saver-playbook.md %}) or [Cart Saver route]({% link _journeys/cart-saver-route.md %}) | -| You want to send a planned one-time message to a selected audience | [Campaigns and broadcasts]({% link _campaigns/campaigns-overview.md %}) | +| You want to send a planned one-time message to a selected audience | [Campaigns]({% link _campaigns/campaigns-overview.md %}) | Sunset Saver can coexist with other playbooks when each one owns a different moment. It should not compete with a more specific signal, and it should stop trying to win back a customer who already returned, replied, opted out, or entered another active flow. diff --git a/_i18n/en/numbers/message-editor-overview.md b/_i18n/en/numbers/message-editor-overview.md index 701dffd..6408582 100644 --- a/_i18n/en/numbers/message-editor-overview.md +++ b/_i18n/en/numbers/message-editor-overview.md @@ -16,13 +16,14 @@ Use the editor to: You may see the editor in places such as: - The inbox, when replying to a customer. -- Campaigns and broadcasts, when creating a one-time send. +- Campaigns, when creating a one-time send. - Routes and playbooks, when writing automated messages. Available tools can vary by channel. For example, SMS supports text and links, while WhatsApp can support richer message types such as locations. ## Related guides +- [Create a campaign]({% link _campaigns/creating-a-campaign.md %}) - [Message editor basics]({% link _numbers/message-editor-basics.md %}) - [Tracked links]({% link _analytics-reporting-attribution/tracked-links.md %}) - [Personalization tags]({% link _audience/personalization-tags.md %}) diff --git a/_i18n/en/numbers/whatsapp-channel-fundamentals.md b/_i18n/en/numbers/whatsapp-channel-fundamentals.md index 13917b6..244f714 100644 --- a/_i18n/en/numbers/whatsapp-channel-fundamentals.md +++ b/_i18n/en/numbers/whatsapp-channel-fundamentals.md @@ -78,7 +78,7 @@ Before launching, test the WhatsApp path from trigger to reply. Confirm what hap Campaigns can send targeted WhatsApp messages to eligible audiences. Keep campaigns focused, use the right template category, and avoid sending more often than customers expect. -Keep reading: [Campaigns and broadcasts overview]({% link _campaigns/campaigns-overview.md %}). +Keep reading: [Campaigns overview]({% link _campaigns/campaigns-overview.md %}). ### Capture tools diff --git a/_i18n/en/troubleshooting-deliverability/troubleshooting-checklist.md b/_i18n/en/troubleshooting-deliverability/troubleshooting-checklist.md index fca32d0..6a573ae 100644 --- a/_i18n/en/troubleshooting-deliverability/troubleshooting-checklist.md +++ b/_i18n/en/troubleshooting-deliverability/troubleshooting-checklist.md @@ -27,7 +27,7 @@ Keep reading: ## 3. Review audience and message setup -If a campaign or broadcast reached fewer people than expected, review the selected audience, segment rules, channel eligibility, timing, and message content. +If a campaign reached fewer people than expected, review the selected audience, segment rules, channel eligibility, timing, and message content. For automations, confirm which playbook or route should have run and whether the customer matched the trigger conditions. diff --git a/_i18n/en/troubleshooting-deliverability/troubleshooting-overview.md b/_i18n/en/troubleshooting-deliverability/troubleshooting-overview.md index 28ce2fc..175d09c 100644 --- a/_i18n/en/troubleshooting-deliverability/troubleshooting-overview.md +++ b/_i18n/en/troubleshooting-deliverability/troubleshooting-overview.md @@ -23,7 +23,7 @@ For SMS-specific limits on new prepaid businesses, keep reading: [SMS sending li For channel setup context, keep reading: [Messaging channels overview]({% link _numbers/messaging-overview.md %}). -## Campaigns and broadcasts +## Campaigns If a campaign result looks lower than expected, review the selected audience, channel, message content, links, timing, and report metrics before comparing results. diff --git a/_i18n/es.yml b/_i18n/es.yml index a48efe7..21153d4 100644 --- a/_i18n/es.yml +++ b/_i18n/es.yml @@ -12,7 +12,7 @@ getting-started: title: Empieza aquí description: Lanza Hellotext en el orden correcto, desde la configuración hasta tus primeros envíos útiles. campaigns: - title: Campañas y broadcasts + title: Campañas description: Planifica, envía y mide mensajes puntuales a audiencias seleccionadas. audience: title: Audiencia y segmentación diff --git a/_i18n/es/analytics-reporting-attribution/analytics-overview.md b/_i18n/es/analytics-reporting-attribution/analytics-overview.md index 87425b8..17c25f5 100644 --- a/_i18n/es/analytics-reporting-attribution/analytics-overview.md +++ b/_i18n/es/analytics-reporting-attribution/analytics-overview.md @@ -6,11 +6,11 @@ Esta sección conecta tres preguntas relacionadas: - ¿Qué acciones de clientes ocurrieron después del mensaje? - ¿Qué ingresos se atribuyeron a Hellotext? -## Reportes de campañas y broadcasts +## Reportes de campañas Los reportes de campaña te ayudan a revisar entrega, interacción, clicks, conversiones, respuestas e ingresos atribuidos para un envío puntual. -Usa reportes de campaña cuando necesites evaluar un broadcast, comparar performance de mensajes o decidir qué mejorar antes de la próxima campaña. +Usa reportes de campaña cuando necesites evaluar una campaña, comparar performance de mensajes o decidir qué mejorar antes de la próxima campaña. Sigue leyendo: [Reportes de campaña]({% link _analytics-reporting-attribution/campaign-reporting.md %}). diff --git a/_i18n/es/analytics-reporting-attribution/campaign-reporting.md b/_i18n/es/analytics-reporting-attribution/campaign-reporting.md index 3d6a08b..6d298da 100644 --- a/_i18n/es/analytics-reporting-attribution/campaign-reporting.md +++ b/_i18n/es/analytics-reporting-attribution/campaign-reporting.md @@ -1,49 +1,95 @@ -Los reportes de campaña muestran entrega, interacción, compras atribuidas e ingresos atribuidos de una campaña entregada. Úsalos para comparar mensajes y canales, revisar la actividad de clientes y entender qué pedidos se vincularon con la campaña según la metodología de atribución de Hellotext. +Los reportes de campaña se generan automáticamente después de la entrega. Reúnen la entrega de mensajes, la interacción rastreada, las compras atribuidas y los ingresos atribuidos para que puedas entender qué ocurrió y qué conviene mejorar. -Para abrir un reporte, ve a **Campañas** y selecciona una campaña entregada. Los reportes están disponibles después de que se entrega una campaña. +Para abrir uno, ve a **Campañas**, abre la vista de campañas entregadas y selecciona una campaña. -## Selecciona el período del reporte +## Elige el período del reporte -El reporte se abre con la opción **Primeros 14 días**. Puedes cambiar el rango de fechas para revisar otro período. +El reporte se abre con **Primeros 14 días** seleccionado. Puedes cambiar a los primeros 7 o 30 días, o elegir un rango personalizado. -El período del reporte controla qué actividad aparece. No extiende la ventana de atribución utilizada para decidir si un pedido corresponde a la campaña. +El período seleccionado actualiza en conjunto las métricas, el gráfico, el embudo, los resultados por mensaje, los desgloses de ingresos y la actividad reciente. Filtra cuándo se registraron esos resultados; no modifica la ventana de atribución utilizada para decidir si una compra corresponde a la campaña. -## Interpreta las métricas principales +Un mensaje de la campaña puede permanecer en la lista aunque sus resultados queden fuera del rango seleccionado. En ese caso, su fila puede mostrar valores en cero hasta que elijas un período que incluya su actividad. -* **Ingresos:** ingresos activos atribuidos a la campaña durante el período seleccionado. -* **ROI:** ingresos atribuidos a la campaña divididos por el costo estimado de entrega de sus mensajes. -* **Conversión:** cantidad de compras atribuidas dividida por los mensajes entregados. -* **Ingresos/mensaje:** ingresos atribuidos a la campaña divididos por los mensajes entregados. -* **CTR:** clics rastreados divididos por los mensajes entregados. +## Interpreta el resumen de la campaña -La conversión no es el porcentaje de clics únicos que realizaron una compra. Se calcula con las compras atribuidas y los mensajes entregados. +Las cuatro tarjetas del resumen responden preguntas diferentes: -## Compara entregas y envíos +* **Ingresos atribuidos:** cuántos ingresos provienen de compras atribuidas a esta campaña durante el período seleccionado. +* **ROI promedio:** ingresos atribuidos divididos por el costo estimado de entrega de los mensajes de la campaña. +* **Conversión:** compras atribuidas divididas por mensajes entregados. +* **Ingresos/mensaje:** ingresos atribuidos divididos por mensajes entregados. -El embudo de entrega muestra cómo avanzaron los mensajes por las etapas de entrega e interacción. Cuando una campaña tiene más de un envío o canal, la tabla de envíos permite comparar mensajes entregados, CTR, ROI, conversión, ingresos por mensaje e ingresos atribuidos. +Selecciona una tarjeta para actualizar el gráfico y ver cómo cambió esa métrica en el tiempo. La conversión se calcula con compras atribuidas y mensajes entregados; no es el porcentaje de personas que hicieron clic y luego compraron. -## Cómo los clics y las entregas contribuyen a la atribución +## Sigue el embudo de entrega + +El **Embudo de entrega de campaña** recorre cuatro etapas: + +* **Enviado:** mensajes de la campaña despachados durante el período seleccionado. +* **Entregado:** mensajes que llegaron a los clientes. +* **Interacción:** mensajes entregados que generaron al menos un clic en un enlace rastreado durante el período. Es una cantidad de mensajes con interacción, no la suma total de clics. +* **Conversión:** compras atribuidas a la campaña. Su porcentaje usa las compras atribuidas divididas por los mensajes entregados, igual que la métrica de conversión del resumen. + +Usa el embudo para detectar dónde cambia el rendimiento. Una diferencia grande entre enviados y entregados apunta a la entrega o la posibilidad de contactar a los clientes. Una entrega saludable con poca interacción apunta más a la audiencia, el mensaje o el llamado a la acción. + +## Compara los mensajes de la campaña + +La sección **Mensajes** muestra la fecha y la vista previa de cada mensaje de la campaña, junto con: + +* **Entregados:** mensajes entregados correctamente. +* **CTR:** clics rastreados divididos por mensajes entregados. +* **ROI promedio:** ingresos atribuidos divididos por el costo estimado de entrega. +* **Conversión:** compras atribuidas divididas por mensajes entregados. +* **Ingresos/mensaje:** ingresos atribuidos divididos por mensajes entregados. +* **Ingresos:** ingresos atribuidos a ese mensaje. + +Esto permite comparar los mensajes reales sin mezclar el rendimiento de los clics con el de las compras. Un mensaje puede tener un CTR saludable y una conversión más débil si los clientes hacen clic pero no completan la compra. + +## Entiende el tiempo de conversión + +**Tiempo de conversión** muestra cuánto demoraron en ocurrir las ventas atribuidas desde el lanzamiento de la campaña, con rangos como el mismo día, 1–3 días, 4–7 días y períodos posteriores. + +El período del reporte filtra cuándo se registró la venta atribuida. Por eso una venta puede aparecer días después de la entrega del mensaje y aun corresponder a la campaña según las reglas de atribución aplicables. + +## Compara ingresos por canal y segmento + +**Ingresos atribuidos por canal** muestra cómo se distribuyen los ingresos atribuidos entre los canales de mensajería disponibles. Úsalo para ver qué canal aportó más ingresos, no solo cuál entregó más mensajes. + +**Ingresos atribuidos por segmento** muestra la distribución entre segmentos de clientes cuando hay datos de segmentación disponibles. Interpreta con cuidado las muestras pequeñas antes de aplicar el resultado a una audiencia futura. + +## Revisa la actividad reciente + +**Actividad reciente** lista eventos rastreados de clientes asociados con la campaña durante el período seleccionado. Puedes buscar un cliente o una actividad y abrir un evento para revisar más detalles. + +Que un evento aparezca aquí no significa automáticamente que haya generado ingresos atribuidos. La compra todavía necesita evidencia elegible de cliente, pedido, origen y tiempo. + +## Separa la actividad de la atribución Un clic en un enlace corto rastreado es evidencia activa de la campaña y normalmente abre una ventana de atribución de siete días desde el clic elegible. El clic no es la única evidencia posible: una entrega elegible de la campaña puede aportar evidencia pasiva dentro de la ventana predeterminada de 24 horas. -Hellotext evalúa la evidencia de origen disponible y su precedencia antes de asignar el pedido. Una fuente de marketing externa reconocida puede tener precedencia sobre la evidencia de Hellotext. Lee [Cómo atribuimos las ventas]({% link _analytics-reporting-attribution/sales-attribution.md %}) para conocer la metodología completa. +Hellotext evalúa la evidencia disponible y su precedencia antes de asignar una compra. Una fuente de marketing externa reconocida puede tener precedencia sobre la evidencia de Hellotext. Lee [Cómo atribuimos las ventas]({% link _analytics-reporting-attribution/sales-attribution.md %}) para conocer la metodología completa. -## Explora los ingresos y la actividad +## Convierte el reporte en una decisión -Según la campaña y los datos disponibles, el reporte también puede incluir: +* **Hay muchos más enviados que entregados:** revisa el consentimiento, que los perfiles de los clientes tengan un canal disponible y los posibles problemas de entrega. +* **La entrega es saludable, pero el CTR es bajo:** revisa la relevancia de la audiencia, la claridad del mensaje y el llamado a la acción. +* **El CTR es saludable, pero la conversión es baja:** revisa el destino, la disponibilidad del producto, la oferta y la experiencia de compra. +* **Hay ingresos, pero el ROI o los ingresos por mensaje son débiles:** compara el costo de entrega, la combinación de canales y la calidad de la audiencia. +* **Un canal o segmento aporta más ingresos:** úsalo como señal para la próxima campaña, considerando también el tamaño de la audiencia y el volumen de mensajes. +* **Las conversiones llegan durante varios días:** espera lo suficiente antes de considerar definitivo el resultado del primer día. -* Tiempo hasta la conversión -* Ingresos por canal -* Ingresos por segmento -* Eventos de entrega e interacción -* Compras y otros eventos rastreados del cliente +## Cuando faltan resultados o parecen incorrectos -Que un evento aparezca en la actividad de la campaña no significa automáticamente que haya creado ingresos atribuidos. El evento todavía necesita evidencia elegible de cliente, pedido, origen y tiempo. +Primero confirma que el período seleccionado incluya la actividad de la campaña. Luego verifica que estén disponibles los enlaces rastreados y los eventos de compra. Las integraciones de comercio compatibles pueden enviar los datos de compras automáticamente; las tiendas personalizadas pueden usar [Hellotext.js o la API]({% link _developers/tracking-events.md %}). -Las integraciones de comercio compatibles pueden enviar los datos de compras automáticamente. Para tiendas y eventos personalizados, usa [Hellotext.js o la API]({% link _developers/tracking-events.md %}). +Si la actividad sigue sin aparecer, consulta [Soluciona señales o actividad faltantes]({% link _troubleshooting-deliverability/troubleshoot-missing-signals-or-activity.md %}). ## Guías relacionadas +* [Crea una campaña]({% link _campaigns/creating-a-campaign.md %}) +* [Buenas prácticas para campañas]({% link _campaigns/campaign-best-practices.md %}) +* [Resumen de campañas]({% link _campaigns/campaigns-overview.md %}) * [Rastrear enlaces en campañas y recorridos]({% link _developers/tracking-on-campaigns-and-journeys.md %}) * [Usar enlaces rastreados]({% link _analytics-reporting-attribution/tracked-links.md %}) +* [Cómo atribuimos las ventas]({% link _analytics-reporting-attribution/sales-attribution.md %}) * [Introducción a Analíticas]({% link _analytics-reporting-attribution/analytics-overview.md %}) diff --git a/_i18n/es/analytics-reporting-attribution/tracked-links.md b/_i18n/es/analytics-reporting-attribution/tracked-links.md index 16f2034..31b63a2 100644 --- a/_i18n/es/analytics-reporting-attribution/tracked-links.md +++ b/_i18n/es/analytics-reporting-attribution/tracked-links.md @@ -14,3 +14,9 @@ Puedes ver nuestra