Skip to content
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

Merged
merged 9 commits into from
Oct 31, 2024
Merged

New article for Banner Cards EA - MERGE 10/31 #8300

merged 9 commits into from
Oct 31, 2024

Conversation

lydia-xie
Copy link
Contributor

@lydia-xie lydia-xie commented Oct 24, 2024

Why are you making this change? (required)

  • New hidden article for Banner Cards EA

Related PRs, issues, or features (optional)

  • N/A

Feature release date (optional)

  • October 31, 2024

Contributor checklist

  • I confirm that my PR meets the following:
    • I signed the Contribution License Agreement (CLA).
    • My style and voice follows the Braze Style Guide.
    • My content contains correct spelling and grammar.
    • All links are working correctly.
    • If I renamed or moved a file or directory, I set up URL redirects for each file.
    • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
    • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

  • Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
  • Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

@cla-bot cla-bot bot added the cla-signed label Oct 24, 2024
@lydia-xie lydia-xie added status: do not merge Could mean research before "in progress" status, or do not merge yet. status: in progress Work in progress. and removed cla-signed labels Oct 24, 2024
@lydia-xie lydia-xie changed the title Banner Cards EA New article for Banner Cards EA Oct 24, 2024
@bre-fitzgerald bre-fitzgerald self-assigned this Oct 24, 2024
_docs/_hidden/private_betas/create_banner_card.md Outdated Show resolved Hide resolved
_docs/_hidden/private_betas/create_banner_card.md Outdated Show resolved Hide resolved
_docs/_hidden/private_betas/create_banner_card.md Outdated Show resolved Hide resolved
_docs/_hidden/private_betas/create_banner_card.md Outdated Show resolved Hide resolved
_docs/_hidden/private_betas/create_banner_card.md Outdated Show resolved Hide resolved
Copy link

vercel bot commented Oct 25, 2024

@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:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Add @bre-fitzgerald as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here and add @bre-fitzgerald as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the Braze team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

@cla-bot cla-bot bot added the cla-signed label Oct 25, 2024
Copy link

vercel bot commented Oct 30, 2024

@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:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Add @lydia-xie as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here and add @lydia-xie as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the Braze team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

@lydia-xie lydia-xie removed the status: in progress Work in progress. label Oct 30, 2024
Copy link
Contributor

@mark-at-braze mark-at-braze left a 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.

_docs/_hidden/private_betas/create_banner_card.md Outdated Show resolved Hide resolved
@lydia-xie lydia-xie removed the status: do not merge Could mean research before "in progress" status, or do not merge yet. label Oct 31, 2024
@lydia-xie lydia-xie changed the title New article for Banner Cards EA New article for Banner Cards EA - MERGE 10/31 Oct 31, 2024
Copy link

vercel bot commented Oct 31, 2024

@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:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Add @rachel-feinberg as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here and add @rachel-feinberg as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the Braze team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

Co-authored-by: Rachel Feinberg <135255868+rachel-feinberg@users.noreply.github.com>
Copy link
Contributor

@rachel-feinberg rachel-feinberg left a 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.

@lydia-xie lydia-xie merged commit 4917019 into develop Oct 31, 2024
1 of 4 checks passed
@lydia-xie lydia-xie deleted the lx-bc branch October 31, 2024 17:03
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/).
Copy link
Contributor

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

Copy link
Contributor

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.
Copy link
Contributor

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.

Copy link
Contributor

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:

  1. You can edit, and we say you shouldn't, or
  2. 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/).
Copy link
Contributor

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
Copy link
Contributor

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

Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants