RGE Studio and Salesforce - Frequently Asked Questions

Beefree App is now RGE Studio!
The email design suite you already know and love just leveled up. We’re working hard to update our help center, but you still may see some references to the old product name.

Overview

RGE Studio works alongside Salesforce Marketing Cloud (SFMC) and Account Engagement (Pardot) as a dedicated email and landing page creation layer. This article answers common questions about how RGE Studio and Salesforce can work together.

General questions

Q: How does RGE Studio fit into a Salesforce marketing stack?
RGE Studio replaces the native builders inside Salesforce. You design in RGE Studio, then push the approved designs directly into your Salesforce platform. Sending, journeys, personalization, and automation stay in Salesforce.

Q: Does RGE Studio replace Salesforce Marketing Cloud or Account Engagement?
No. Your Salesforce platform continues to send emails, manage lists, run journeys, and handle automation. RGE Studio is additive: it gives your team a better place to create and govern email content, with a clean path to deploy it into Salesforce.

Q: We have existing SFMC or Pardot templates. Do we have to rebuild them in RGE Studio?
No. RGE Studio's HTML Importer brings existing email templates directly into the builder. Upload your HTML file, and RGE Studio converts it into a visually editable design, ready to adjust in the drag-and-drop builder without touching code.

Please refer to our HTML Importer documentation for full details. 

Setup and technical requirements

Q: What do I need to connect RGE Studio to Salesforce Marketing Cloud?
You need an active SFMC account with Content Builder access. The SFMC connector is available on all RGE Studio plans. To set it up, authenticate with your SFMC credentials and select the Content folder where exported emails will land.

Credential requirements (API user setup, permissions, installed packages) vary by SFMC configuration. Our support documentation can walk you through setup for your environment.

Q: What do I need to connect RGE Studio to Account Engagement (Pardot)?
You need access to the Classic Account Engagement interface, not just the Lightning (enhanced) email experience. The Account Engagement connector is available on all RGE Studio plans, and authentication uses OAuth with your Salesforce credentials.

You need Account Engagement permissions to access templates in the Classic editor. If some team members send one-off emails via Sales Cloud Lightning without an AE license, see the one-off sends question below for a known workflow limitation.

Q: Can we use RGE Studio for one-off sales emails sent through Salesforce Lightning?
It depends on the size of the email designed in RGE Studio. Salesforce Lightning Email Templates have a 10,000-character limit per component. A typical RGE Studio HTML email exceeds this limit.

Q: Does RGE Studio work with Distributed Marketing (Marketing Cloud + Sales Cloud)?
Yes, if you have the RGE Studio Enterprise plan. This configuration requires a special setup in RGE Studio. Talk to Sales or your account manager for more information.

Q: What does our security team need to know about data moving between RGE Studio and Salesforce?
RGE Studio focuses on email creation, not on processing the customer data inside your Salesforce platform. Your subscriber records, data extensions, segmentation logic, and sending activity all stay in Salesforce. 

Salesforce Marketing Cloud (SFMC)

Q: How does the RGE Studio connector work with Marketing Cloud?
Once connected, you design your email in RGE Studio and push it directly into SFMC's Content folder with one click. It lands in Marketing Cloud as an HTML email, accessible via Content Builder and ready for a send, journey, or automation. Your SFMC sending infrastructure, data extensions, and Journey Builder logic stay untouched.

You can also export the HTML from RGE Studio and paste it into SFMC manually. Both paths deliver the same production-ready HTML; the connector just removes the manual step and saves time.

Q: Can my team still use AMPscript after exporting from RGE Studio?
Yes. Place AMPscript in RGE Studio using merge tags or HTML blocks. SFMC renders AMPscript server-side at send time, so the logic runs normally once the email is in Content Builder.

Note: For complex AMPscript functions like ContentBlockByKey(), use a Code Snippet block in SFMC after export. This two-step workflow (design in RGE Studio, finalize AMPscript in SFMC) is well established among technical SFMC users.

Q: When RGE Studio exports to SFMC, what email type does it create?
RGE Studio creates an HTML Email, not a template-based email. This means the email is a complete, self-contained HTML file, and it isn't directly editable in SFMC's drag-and-drop WYSIWYG editor after export.

To make post-export changes, edit the source HTML in SFMC's Code View, or go back to RGE Studio, make the change there, and re-export. For most teams, the RGE Studio workflow avoids the need to touch the email in SFMC after export.

Note: You can convert an RGE Studio HTML export into an SFMC template-based email by pasting it as a template instead of an HTML email, which allows SFMC content blocks to be added. This path is more involved and recommended for advanced users. We've tested it and confirmed SFMC doesn't alter the HTML, but it requires some familiarity with Content Builder.

Q: We use Dynamic Content in SFMC with editable content regions. Can RGE Studio support that?
Yes, with the right export method.

To create editable content regions in an SFMC-compatible template built in RGE Studio: create an empty row, drag in an HTML content block, and inside that block add a <div data-type="slot"> with a unique data-key attribute. This tells SFMC you want an editable content region in that row. 

Then copy and paste the HTML into SFMC as a template. Those regions become available in SFMC’s template-based email editor. There you can set default content and define rules-based dynamic content variations. This option is not available when using the connector in RGE Studio.

One caution worth knowing during evaluation: if editors then use the SFMC WYSIWYG editor to change that template, the HTML will be modified. The HTML that SFMC generates isn't Outlook-optimized, which can introduce rendering issues.

Q: We track links with tracking aliases in SFMC. Can we do that in RGE Studio?
First, a distinction worth making: tracking aliases and tracking pixels are different things. RGE Studio doesn't offer tracking pixels, a feature you may have seen from analytics vendors like Litmus or Validity. Tracking aliases, on the other hand, are supported. This workflow requires an Enterprise account in RGE Studio.

Aliases let you label individual links so you can tell exactly where a contact clicked, for example distinguishing a hero image click from a button click when both point to the same URL. Set this up in RGE Studio through Custom Attributes:

1. In settings, go to Builder preferences and enable custom attributes in the builder.
2. Click Manage custom attributes and create two attributes: Alias (target "link," with a blank value you fill in via an open text field in the editor) and Conversion (target "link," with true/false values shown as a dropdown in the editor).
3. Once set up, an Attributes section appears when you edit any link in the builder. You can assign different aliases to each link independently, even when two links share the same URL. You can also set conversion tracking per link.

Q: What about SFMC-specific tracking requirements, like open tracking pixels, profile center links, and unsubscribe links?
SFMC requires certain elements for commercial sends: an unsubscribe link, a profile center link, a physical mailing address, and optionally an open tracking pixel. Add these to your design before exporting, since they don't auto-populate, or add them in SFMC afterward.

Most teams create a saved row in RGE Studio for a standard footer (organization address, merge tags, and unsubscribe link) and include it in every template. For the open tracking pixel, create a merge tag in RGE Studio settings and insert it as a hidden 1px text block. See our connector set-up guide for more information.

Q: We use Dynamic Content and A/B testing in SFMC. Does RGE Studio interfere with that?
No. Dynamic Content and A/B testing are SFMC-level features that operate after the email is deployed. RGE Studio delivers the HTML, and SFMC handles everything at send. As long as the structural HTML stays intact, SFMC's personalization and testing layers work as normal.

Q: Can we control asset naming in SFMC, like matching the Customer Key to the email name?
Yes. RGE Studio can support workflows where the Customer Key in SFMC matches the email name you set in RGE Studio, instead of relying only on system-generated values. This helps teams that reference assets programmatically or want more predictable naming conventions in Content Builder.

Q: Our SFMC emails live inside Journeys. Does updating a design in RGE Studio propagate automatically?
No. When you re-export an updated design from RGE Studio to SFMC, it creates a new or updated HTML asset in Content Builder. If that email is already assigned to an active Journey, you'll need to manually reassign the updated asset inside the Journey for the change to take effect. 

Q: We're evaluating or migrating to Marketing Cloud Next. Does RGE Studio work with that?
Not yet through a direct connector. Marketing Cloud Next is a new platform built on Salesforce Core, and a native RGE Studio integration doesn't currently exist. If your team runs exclusively on Marketing Cloud Next today, this is a confirmed gap for now.

Account Engagement (Pardot)

Q: How does the RGE Studio integration work with Account Engagement?
You design your email in RGE Studio, then export directly to Account Engagement using the native connector. The email lands in the Classic email editor as a template, ready to use for list emails or automation. Your Pardot merge tags (HML syntax, like {{prospect.first_name}}) carry through the export and render correctly at send time.

Q: Does RGE Studio only work with the Classic Pardot editor?
Yes. The RGE Studio connector exports to the Classic Account Engagement editor, found under Content > Email Templates in the Classic Pardot interface. It doesn't integrate directly with the Lightning Email Builder, also called the Enhanced Email Experience.

If your team has fully migrated to the Lightning Builder, the current connector doesn't cover that workflow yet. HTML copy-paste is technically possible but impractical, since the Lightning Builder has a 10,000-character limit per component and a standard RGE Studio email typically exceeds it.

Q: Do Pardot personalization tokens and merge fields work when I export from RGE Studio?
Yes. Pardot uses Handlebars Merge Language (HML), like {{prospect.first_name}} or {{Organization.Address}}. Place these directly in RGE Studio using the merge tags feature, and they carry through to the exported HTML. Pardot resolves them at send time as normal.

Account Engagement requires a physical mailing address and an unsubscribe mechanism in every commercial email. If your org has the default Pardot footer disabled or overridden, add {{{Organization.Address}}} manually to your design before exporting, or the send will be blocked. If the default footer is enabled, these elements are added automatically at send.

Q: Can I still use Account Engagement's dynamic content rules?
Yes. Configure and manage dynamic content logic in Account Engagement itself, not inside the email design. RGE Studio delivers the HTML structure, and Pardot's dynamic content rules operate on top of it at the template or send level. The two work together without conflict.

Q: We use Engagement Studio for B2B nurture sequences. Does RGE Studio affect how those work?
No. Engagement Studio is entirely separate from email creation in Account Engagement. RGE Studio's role ends when the email template lands in Account Engagement. Everything Engagement Studio does with that template, including branching logic, timing, and prospect scoring triggers, works exactly as before.

Q: Salesforce is pushing Account Engagement customers toward Marketing Cloud Next. What does that mean for the RGE Studio integration?
The Classic Account Engagement connector continues to work as your team moves toward Marketing Cloud Next. A native Marketing Cloud Next connector doesn't exist yet.