* Marketing Cloud Engagement *

@Nagaraju Vadlamudi

Sendlog DE will only show or add records when a send has occurred. 

It is not recommended to update Sendlog DE in any other way. (i.e. using SQL, import etc) 

As you already have the ControlGroup "true" in the source DE, you can apply a filter and run it via automation to review the Control Group audience.  

Additionally, as you have highlighted that you are using "Random Split" in Journey for 10% control group exclusion, I assume that the number of records being processed is >1000, otherwise Random Split may work unexpectedly. See this article for better understanding -

Hi @Ajith M S

Most of these are read-only helpers that sit on top of the SFMC UI, so they're low-risk to try. 

Navigation and discovery 

• SFMC Companion lets you click through Automations, Queries, Data Extensions and more to see where they're saved and what uses them. For example, clicking a Data Extension shows which Queries target it and which reference it in their code. It's the most useful one for untangling an unfamiliar account. Chrome Web Store
• DESelect Search in SFMC is a free extension for finding things that native search handles poorly. Native search only scans one selected folder at a time. It can search across business units or just your current one. The listing carries a note that because of recent Google security updates, it only works if the AppExchange version is already installed, so check that before relying on it. DESelect Search in Salesforce Marketing Cloud - Chrome Web Store +2
• SFMC Scout (recommended in the Trailblazer thread) gives you a side-panel search across Data Extensions, Automations, Journeys, Emails and Content Builder assets.

Development and debugging

• SFMC Inspector (from the thread) covers Data Extension exploration, automation-to-DE mapping, Journey discovery and SQL linting.
• SFMC Dev Studio (from the thread) adds AMPscript/SSJS syntax highlighting, linting, snippets and function references.
• SFMC IntelliType offers AI-powered code completions, snippet management, and contextual assistance for AMPscript, SSJS and SQL. It also includes Data Extension tools for finding and opening a Data Extension quickly without any API configuration. Chrome Web Store Chrome Web Store
• Marketing Cloud  Developer Tools is a DevTools panel. Its features include exposing Publication List IDs and Journey Builder activity keys, showing Data Extension and Journey details, and surfacing more detailed error messages. One reviewer said it doesn't work in their org and another said it's hard to read in dark mode, so test it in your own account. Extpose

Journey Builder and day-to-day admin

• MCX (Marketing Cloud eXtension) covers a lot. It can compare Journey versions and Data Extension configurations side by side, map object relationships visually, and send push notifications directly from Journey Builder. Chrome Web Store
• SFMC Automation Viewer lets you view automation details without pausing active automations. That's handy for checking a live automation. Chrome Web Store
• There's also a Journey Builder email-preview extension that sends previews for every email in a journey at once. I only saw it in Chrome Web Store related-listing snippets, so I don't have its exact name.

Things to check before rolling these out

• Some of these are small third-party tools, and they act with your logged-in SFMC session. Companion notes it's limited by the Marketing Cloud user's roles and permissions, but check each one's requested permissions and privacy disclosures. That matters most on client or production accounts, where you should get sign-off first. Chrome Web Store
• Several of these overlap (Companion, Scout and DESelect all do search), so one or two are usually enough.
• Some listings are old, so confirm each is still maintained before depending on it.
• For serious AMPscript/SSJS work, the Trailblazer answer also suggests Salesforce's AMPscript extension for VS Code. That gives you local development instead of coding in the browser.

 I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hi Rebeca!

I wouldn’t assume the WhatsApp Chat Messaging subscription itself expires just because it was created through an Automated Import Definition. The important distinction is between the channel subscription/opt-in status and whether the contact is still eligible and available for the send.

If contacts are successfully receiving messages initially but later stop receiving them, I’d check the subscriber’s current WhatsApp subscription status, opt-in/consent data, and whether the Data Cloud segment/activation is still including the contact.

For the automation, running the import regularly can be useful to keep the WhatsApp audience synchronized with your latest opted-in population, especially when opt-in/opt-out status can change. However, I’d avoid re-subscribing everyone blindly; make sure the source data represents the current consent state.

If you can share what changes in the contact’s WhatsApp subscription status when the later send fails, that would help determine whether this is an expiration issue, consent change, or audience/synchronization issue.

@Jackie McDaniels I integrated it once, however, its been awhile. If you want to update the secret in ON24 platform then below article will be helpful - https://support.on24.com/hc/en-us/articles/21420785350683-Salesforce-Marketing-Cloud-Integrations-Overview#sfmc

Click on the SFMC connection tab on this page and scroll down to see where you can update the client ID and client secret. 

Hope this helps.  

Hi Jackie!

Yes, this can be handled with the Distributed Marketing Phrases Block, but there is an important limitation: the Phrases Block lets the business user select phrases, with up to 12 phrases per block, but it isn't designed as a true multi-select field. 

For your use case, one workaround would be to use multiple phrase selections as inputs and then use AMPscript to determine which larger content sections should be rendered based on those selections. Distributed Marketing supports AMPscript for creating personalized content. 

If the requirement is specifically “select multiple predefined options and combine the corresponding content”, I’d probably avoid trying to force the standard Multivariate Block to do it, since that block is designed around selecting a value/variation rather than a multi-select combination. 

If you share an example such as Options A + C selected → show Content A + Content C, I can suggest an AMPscript structure for the template. 

Hi Andreea!

There is actually a recent Salesforce guidance specifically covering LLM crawler/bot traffic and CloudPages billing, so your approach is aligned with the documented mitigation strategy.

Salesforce confirms that a CloudPages impression is counted when the request returns HTTP 200, including successful requests from bots/crawlers. A non-200 response therefore avoids that CloudPages impression charge.

Salesforce also documents an SSJS-based approach to detect known bot User-Agents and terminate the request before a successful page response. The guidance specifically recommends putting the check at the beginning of the page.

For your three questions:

• Delegated domains: CloudPages doesn't provide native IP restrictions or authentication. If the domain is fully delegated to Salesforce, you don't have the same edge-WAF control as you would when your own DNS/CDN sits in front of the page.
• RaiseError/500: Salesforce's billing documentation states that successful 200 OK requests are CloudPages impressions. So a request terminated with a 500 should not be counted as a CloudPages impression, but I'd still have Support confirm the behavior against your specific account/billing report.
• Alternative architecture: Salesforce's current guidance also suggests using Code Resources for endpoints that don't need to render a normal landing page. Code Resources do not consume Super Messages, which can be useful for processing/API-style endpoints.

For self-hosted domains, blocking the traffic at Cloudflare/Akamai/AWS WAF before it reaches Salesforce is still preferable because it prevents the request from reaching the CloudPages infrastructure in the first place.