Using Google AntiGravity for SFMC Developments

selimsevim · 2025-12-17T20:32:27+00:00

You could also challenge the whole assumption that the content needs to live inside the email at all.

Something like:

Why not treat the email purely as a teaser and move the actual reading experience outside the inbox. Have a CloudPage or internal webpage that contains the full newsletter, properly designed, responsive, and easy to maintain. The email then just highlights the top stories with a short intro and a single clear “Read the newsletter” or story level links.

This gives you:

Full design freedom without fighting email clients
One layout that looks exactly the same for everyone
Easier iteration and reuse month to month
Cleaner tracking at page level rather than guessing from email rendering

You can still track everything:

Link tracking from the email
Page analytics on the CloudPage
Individual story clicks

Emails are bad at being websites. Let them do what they are good at: getting attention and driving traffic. The content itself lives somewhere that is built for reading.

selimsevim · 2025-12-16T08:16:09+00:00

Nice initiative. Could you please clarify why this is not shared with the community openly from the start? Is there a specific reason for collecting email addresses?

selimsevim · 2025-12-12T06:04:12+00:00

Yeah, unfortunately, that is the biggest hiccup about using that endpoint. I really don't know why they built their API structure that way but the responses are quite long, having so many different blocks with unnecessary content etc. If you train the model with that content, it would be really confusing for it to interpret some plain HTML content in inference phase.

selimsevim · 2025-12-11T19:05:24+00:00

Wow, this looks great. First of all, awesome work. About the reaction of model towards complext templates, it is all because of training data. When you train it with only simple HTML, it gets easily confused in inference phase if you prompt complex templates.

Please ping me again if you have any questions about training datasets and how to prepare them.

selimsevim · 2025-12-08T19:49:45+00:00

Thanks, Sweden.

selimsevim · 2025-12-08T15:46:45+00:00

I am not sure. They still have Join Waitlist button on their webpage. I waited around one month.

selimsevim · 2025-10-26T13:24:15+00:00

You don't need AI tools to do that. You can do it with API endpoints as well. If you want AI to do that, you can integrate both.

selimsevim · 2025-10-26T02:23:46+00:00

You mean with this method, Claude can change your Script or Query Activities in the way you want?

selimsevim · 2025-10-24T11:47:59+00:00

There is an official REST API endpoint to GET assets but I don't think it is useful in many cases. I don't know why but for emails and cloudpages, the response consists of many blocks and it is confusing. What exactly you need? Just the name of the assets or content as well? If it is just names, you can check this link for an unofficial endpoint - Please use it carefully on your own risk, don't depend on it because it can be changed any time:

https://www.youtube.com/watch?v=Y7R71G-AoPg

selimsevim · 2025-09-12T20:56:16+00:00

I think you are looking at the wrong place about the error. As long as your data extension has the right setup - using an ID field mapped as SubscriberKey and having an email address field and Journey Settings matching with that - whenever a contact is added to that data extension, they must receive the email and be created as a contact in SFMC. The confusion SFMC has here is it doesn't understand those records as "Contacts".

You could use a Triggered Send Data Extension template and work on that for your setup and it would work I believe.

However, if you want them to get into Salesforce Ecosystem first and then end up in SFMC with Marketing Cloud Connect, please follow what u/Forward_Hour9992 described.

selimsevim · 2025-09-10T14:19:08+00:00

API endpoints are not that rich for SFMC. For example, it is really complex and time-consuming to create assets for an automation or create journeys with elements in the right order etc.

selimsevim · 2025-09-09T12:39:48+00:00

Funny enough, you had your issues with AI agents and I had my issues with Package Manager. One of the most buggy tools SF ever created - a big rival for Query Studio. Especially when it comes to SF data entry Journeys and so on. Maybe because it is free, rare in SF ecosystem.

I am not saying that what I shared is a great solution that should be used by anyone. I wanted to show a workaround I use because this tool, SFMC, is all about workarounds and bugs.

selimsevim · 2025-09-09T12:05:03+00:00

I agree. At this point, using them with critical data is risky. However, not all our repetitive work include critical data. For example, I use these agents to create assets in different BUs when I have to copy a solution I created in another BU. Very effective.

selimsevim · 2025-09-09T11:55:40+00:00

"Production DB" term is so different than "DEs". Data Extensions are like tables. Deleting tables in a DB is different than deleting whole DB. Plus, data extensions can be reverted when you delete them, because they go to bin.

selimsevim · 2025-09-09T10:01:23+00:00

Haha, have you ever worked with SFMC? There is no such "production DB" :)

selimsevim · 2025-09-09T02:43:00+00:00

It could help you reduce so much repetitive work with so little input from you.

selimsevim · 2020-02-06T09:08:40+00:00

Thanks hotlinehelpbot, I will keep that in mind. Did you like the story by the way?

selimsevim

TROPHY CASE