MomentMarketer Community Group

🪟 It's time for @* Marketing Cloud Engagement * SQL Window Functions: https://mateuszdabrowski.pl/docs/salesforce/marketing-cloud-engagement/sql/sql-window-functions/

Built for SQL power users, with a real-life example in every section: the latest open of each subscriber, the days between two orders, your top 10 customers. Most of us build those with a chain of Query Activities and a staging Data Extension. Deduplication, top N lists and running totals - window functions do it in one query, with a few traps along the way: 

🔵 Nearly everything works. 

ROW_NUMBER, RANK, NTILE, LAG and running totals all run in MCE. Even IGNORE NULLS from SQL Server 2022 works, so the last coupon each subscriber used takes a single function. 

🟠 Ties pick a random winner. 

ROW_NUMBER over two orders from the same day keeps either of them, and the next run can keep the other. There is no error, and your Data Extension changes between runs. End every ORDER BY inside OVER with a unique column. 

🔴 Filtering needs a subquery. 

WHERE ROW_NUMBER() OVER (...) = 1 fails with "Windowed functions can only appear in the SELECT or ORDER BY clauses." The usual fix, a WITH, fails too, as the MCE syntax validation wants SELECT as the first word (sic!). A subquery in FROM does the job. 

Encountering issues? My free and open source

flags them before you run anything and offers fixes with one click.  

Writing SQL with Claude instead? The newly updated

🤖 Build real expertise for the Agentic AI era. 

Trailhead Journeys are now available across 10 Salesforce products empowering you to move from fundamentals to advanced expertise with a progressive, step-by-step curriculum. 

Newly added journeys:

• ⚡ Headless 360 platform
• 📈 Agentforce Marketing
• 👥 Agentforce Service 
• 🛒 Agentforce Commerce
• 🔌 Omnistudio

Skip the search. Start the journey 👉 trailhead.com/trailhead-journeys

Hello Everyone, 

I'm setting up Marketing Cloud Next (Advanced Edition) in a new org on Winter '27 and I'm stuck on one prerequisite. 

In Setup > Salesforce Go > Marketing Cloud Next > Initial Setup > Complete the Prerequisites, every step is complete except "Enable Marketing Objects", which shows: 

"We couldn't set up Marketing Objects. Ask your Salesforce admin for help. Enable Marketing Objects and ensure the Marketing Data tab is added to the Marketing Application." 

What I've already checked: 

- Data Cloud is enabled, the CRM connector is created, the default email channel exists, and the data space is set to default 

- My admin user has the Marketing Cloud Admin and Data Cloud Admin permission sets 

- Marketing Cloud Admin includes the Manage Marketing Objects permission (ManageMarketingObjects) 

- The Marketing app is installed and working 

- There is no Marketing Data or Data Management tab in the App Launcher or in the System Administrator profile's Object Settings 

- Setup Quick Find returns nothing for "Marketing Objects" 

- This org isn't eligible for Support cases, so I'm asking here 

My questions: 

1. Has anyone hit this, and found a way to re-run or manually enable Marketing Objects? 

2. Are Marketing Objects provisioned in demo, developer, or trial orgs, or only in paid Growth/Advanced orgs? 

Screenshot of the error is attached. Thanks in advance! 

{} MCE SQL Reference doesn't mention JSON at all. @* Marketing Cloud Engagement * SQL reads, changes and builds it anyway. Learn how: https://mateuszdabrowski.pl/docs/salesforce/marketing-cloud-engagement/sql/sql-json-functions/

API payloads, CloudPages submissions and product feeds land in your Data Extensions as JSON. Most of us reach for SSJS to read them and fight against performance, but a Query Activity can do much of that work itself, with a few traps along the way: 

🔵 It builds JSON, too.

Despite documentation, the silently updated SQL Server behind MCE supports 2022 feature set: JSON_OBJECT, JSON_ARRAY and JSON_PATH_EXISTS. FOR JSON PATH turns each subscriber's abandoned cart into one field your email can loop over. 

🟠 Reading has a limit.

JSON_VALUE returns NULL for any value over 4000 characters. 4000 works, 4001 doesn't, and there's no error. OPENJSON would lift the limit, but the MCE syntax validation treats it as a Data Extension name (sic!). 

🔴 Broken JSON stops everything.

One truncated payload fails the whole Query Activity, and the Action Log says only "Automation failed due to system error." Wrap your reads in ISJSON, and the broken records return NULL instead. 

Every output in the article comes from a live test in my Query Studio replacement - SQL Studio - which just got version 1.2: save results straight to a new Data Extension, share snippets across your Business Unit and add a JOIN to your query in one click.

More to come, so keep on querying!

https://jobs.micro1.ai/post/95262281-9341-44dc-a5b1-4361ed9daaab?referralCode=2453214a-1a08-493f-95bf-12aa5402008d

Role Title: Salesforce Specialist 

Role Type: Contractor 

Location: Remote 

micro1 is engaging Salesforce Specialists to contribute expert insight and capabilities to a critical customer project. In this role, you'll apply your expertise to help train next-generation AI systems. Your work will shape how models learn, reason, and perform through high-quality, real-world input. No prior experience in AI is required — your domain knowledge is what matters. This opportunity emphasizes a high standard of written and verbal communication, enabling effective collaboration in a remote environment. 

Scope of Work 

Complete and review realistic workflows within Salesforce. 

Work with leads, contacts, accounts, opportunities, and other CRM records. 

Create and manage Salesforce reports and dashboards. 

Use Salesforce Flow and automation features to support common business processes. 

Manage and organize CRM data accurately. 

Explore Salesforce features and identify common real-world use cases. 

Clearly document the steps needed to complete different Salesforce workflows. 

Review workflows and provide feedback based on your Salesforce experience.

📬 Marketing Cloud Next takes care of your sending IPs automatically. But that doesn't mean you're off the hook for deliverability: https://mateuszdabrowski.pl/docs/salesforce/marketing-cloud/config/ip-warming-deliverability/

On @* Marketing Cloud Engagement * you have full control over deliverability, for good and for bad. On @* Marketing Cloud Growth & Advanced * the experience is more streamlined, but also controlled by Salesforce. You start on a shared pool of IPs, and you work your way out of it. 

Once you cross ~5M emails/type/month, Salesforce rewards your achievement with a dedicated IP, and warms it on its own. Not much to do for you. No schedule, no throttling, no configuration. Marketing Ops dream? Almost. 

There are still some important tasks on you: 

🔵 You still need basic configuration to enable your first sends. And it's a bit stricter than it was on MCE. 

🟠 IP reputation != Domain reputation.  A new sending domain (might) still need its own warming plan. 

🔴 Monitoring is a must. It already was. Then it got must-er with tighter ESP bounce & complaint rate requirements. And now it is must-est with lower control over IPs and the impact of being demoted to the Gray Pool.  

Full mechanics, the prerequisites checklist, and the monitoring options with setup guides are available now on my page.

Secure your Agentblazer Status and stay ahead of the curve.

More content has been added to the Champion, Innovator, and Legend trails! Plus, the new change log feature makes it easy to track what’s new to grow your skills and keep pace with AI. 

 Skill up today:

trailhead.com/agentblazer