-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New article for Banner Cards EA - MERGE 10/31 #8300
Conversation
@bre-fitzgerald is attempting to deploy a commit to the Braze team on Vercel, but is not a member of this team. To resolve this issue, you can:
To read more about collaboration on Vercel, click here. |
@lydia-xie is attempting to deploy a commit to the Braze team on Vercel, but is not a member of this team. To resolve this issue, you can:
To read more about collaboration on Vercel, click here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last change, then good to go.
@rachel-feinberg is attempting to deploy a commit to the Braze team on Vercel, but is not a member of this team. To resolve this issue, you can:
To read more about collaboration on Vercel, click here. |
Co-authored-by: Rachel Feinberg <135255868+rachel-feinberg@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm! Made a few minor edits and left a suggestion for capitalization.
3. Name your campaign something clear and meaningful. | ||
4. Add teams and tags as needed. Tags make your campaigns easier to find and build reports out of. For example, when using the Report Builder, you can filter by the relevant tags. | ||
5. Select a [placement](#prerequisite-determine-placement) to associate with your campaign. This is where the Banner Card will appear in your app or site. | ||
6. Add and name as many variants as you like for your campaign. You can choose different message types and layouts for each added variant. For more information on variants, refer to [Multivariate and A/B testing]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can choose different message types and layouts for each added variant.
This isn't possible with banners
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Specifically--you can make different layouts in the DnD editor, but there isn't any "choosing" or "types" like Content Cards.
1. Go to **Settings** > **Banner Card Placements**. | ||
2. Give your Banner Card placement a name. | ||
3. (Optional) Add a description to explain where this Banner Card is intended to be placed. | ||
4. Enter a unique placement ID. Work with your developer team to define this ID, because they will need to use it during the integration. Avoid editing your placement ID after launch, as this can break the integration with your app or website. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Avoid editing your placement ID after launch, as this can break the integration with your app or website.
@mark-at-braze something to think about, but maybe placement_ids should be uneditable once set. If no campaigns are assigned the placement is deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with either:
- You can edit, and we say you shouldn't, or
- You can't edit at all.
This section was originally "you can edit, but don't," which was no good IMO.
I don't see any cons to making them uneditable, but we can add that as something to look at post EA.
| **Primary Conversions** | Includes both the count and rate of conversions for the [primary conversion event]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events/#primary-conversion-event). The primary conversion event is determined when you build the campaign. {::nomarkdown}<ul><li><i>Conversions</i> are the number of times a user performs an event after clicking on the Banner Card. Each user is only counted once.</li><li><i>Conversion Rate</i> is the percentage of times the conversion event occurred compared to all recipients of a message. <br> <i>(Conversions) / (Unique Impressions)</i></li></ul>{:/} | | ||
{: .reset-td-br-1 .reset-td-br-2} | ||
|
||
For a full list of metrics, definitions, and calculations, refer to our [Report Metrics Glossary]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this report metrics page be updated with a checkbox for Banners?
Placement IDs are unique per workspace. | ||
{% endalert %} | ||
|
||
## Step 1: Create your campaign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some messaging should be added that connected content nor promo codes are supported by banners
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lydia-xie Can you maybe add a section at the end of the doc under best practices that these aren't supported?
Why are you making this change? (required)
Related PRs, issues, or features (optional)
Feature release date (optional)
Contributor checklist
Submitting for review
If your PR meets the above requirements, select Ready for review, then add a reviewer:
braze-inc/docs-team
as the reviewer.braze-inc/docs-team
instead.Thanks for contributing! We look forward to reading your work.