Skip to main content

#Journey Builder6 人がディスカッション中

🚀 Available for Freelance Projects | Salesforce Marketing Cloud (SFMC)

Salesforce Marketing Cloud Specialist with 3+ years of experience delivering automated, personalized, and CRM-driven marketing solutions.

Expertise: 

✔ Email Studio | Journey Builder | Automation Studio 

✔ AMPscript | SQL | HTML/CSS  

✔ Audience Segmentation & Dynamic Personalization 

✔ SFMC + Salesforce Sales Cloud Integration 

✔ Customer Journeys & Campaign Automation

Open to short-term, long-term, and remote freelance opportunities.

Feel free to connect or message to discuss your SFMC requirements.

#Salesforcemarketingcloud #SFMC #Salesforce #Email #AMPscript #Journey Builder #Freelance Project Work #Freelancing Work #Freelancing

0/9000

Hello community: I have a question regarding when you have only one business unit. How do you handle API event tests that might be involved in a Java build? For example, how would a password reset process work? Do you test and delete contacts? Do you use a dedicated test journey?  Thanks      

2 件の回答
  1. 5月20日 22:05

    Thanks @john wick Thank you very much. By "deleting contacts" I meant leaving an automation. Regarding trips, is it common to have one test and one real trip, or does it depend on the case? For api, the attribute can be used, but if it's later deleted, I understand it's not necessary. I didn't understand the part about deletion.

0/9000

I'm creating a Journey with an engagement split. The mail has a CTA link to generate a call from Sales Rep. If the the contact clicks, the call activity should be generated immediately, but if not click, should wait a week before sending another email. How can I get this? Thanks!   

1 件の回答
0/9000
How do I remove duplicates in Journey Builder before sending an email? All our data extensions (source data extensions, too) have the ID as the subscriber key so there are duplicate email addresses in all the data extensions. Automation Studio has this feature already but I need it in Journey Builder since we resend to the people who haven't opened the email.
5 件の回答
  1. 4月15日 14:31

    Hey, you can do this with the journey builder settings using journey is no re-entry, but this only works if your contactID (your primary key) is the subscriber key. 

0/9000

When we use test simulator in Journey builder after validation, and use update contact activity to test the Journey sequence. Does it update the record in realtime? 

Thanks in advance!!

3 件の回答
  1. Florin Valean (Creation Technology Solutions Limited) Forum Ambassador
    2023年4月5日 18:33

    Hi Tejasvi,

    Update Contact updates the record in real time only in the live journey.

    In Test mode Update Contact is skipped.

    On Testing Summary scroll down to Test Behavior option under the Choose Contacts button and view the settings. See my screenshot below:Hi Tejasvi,Update Contact updates the record in real time only in the live journey.In Test mode Update Contact is skipped.

0/9000

I', very new at marketing cloud and I just finished a journey builder, that both checks the status value and isMarketing__c value of cases 

 

I have a normal flow that after a bunch of important validations, sets the custom field to true if it needs to be tackled by marketing cloud, and my journey which I have selected both as created and updates cause I need to process cases when status is "New" or "Closed" and custom field is true 

 

But I just found out searching for information before activating it, that apparently journey builder will launch every single time a case has another field updates if it is already New/Closed and True, cause it doesn't validate if the 2 fields have just changed to said values. 

 

My question is, is this true? and if yes, how can I tackle this issue (I can't just deny re-entry cause the contact should be able to create multiple cases and receive email for each of them), also will the fact the custom field is update to true in a flow affect how journey "receives" the case?     I haven't seen anywhere the choice of "only when fields change to meet the criteria" or something similar

1 件の回答
0/9000

Hello, everyone.  I have structured a Journey that sends WhatsApp messages. When sending these messages, I need to understand which of my subscribers have opened the message.     To do this, I tried several methods, such as the Intelligence Report section, which allows me to see the total number of opens or sends for that specific message, but I was unable to associate a SubscriberKey with each opens or sends. So I can't figure out which subscribers actually opened the message.    I thought of another solution, which was to query the Marketing Cloud Data View. I can access the journey and the specific activity, but I can't track down the subscriberKey to understand who the Open numbers I see in the reports refer to, considering that the Data Views _open, _send, and _click refer ONLY to emails.    Can you help me by suggesting an alternative? Or can you confirm that i have done everything possible and that there is no alternative?  

1 件の回答
0/9000

I have a journey with an automated data extension that repeats hourly. When a new person is found it adds them in the journey and sends them an email. How do I avoid these emails being sent out really late or really early in the morning? Do I add a wait duration before the email?   

1 件の回答
  1. 2025年11月18日 17:00

    To avoid emails being sent too early or late, use a Wait Until activity or configure Contact Scheduling / Blackout windows

    in journey settings. This ensures contacts only receive emails within your defined time range. 

     

    Use a Wait Until Activity

    Place a Wait Until immediately before the Email Send.

    • Set it to release contacts only during a certain time range (e.g., 8 AM–8 PM local time).
    • Journey Builder will hold contacts until the next allowed window.

    Refer: https://help.salesforce.com/s/articleView?id=mktg.mc_jb_wait_activity.htm&type=5

0/9000
I am new to marketing cloud and need to understand what does the each of the below component mean in the exclsuion sript.

 

ROWCOUNT(LOOKUPROWS("Exclusion_DATA_EXTENSION_NAME","EMAIL_ADDR_FIELD_NAME", EMAILADDR))>0
3 件の回答
  1. 2025年11月18日 16:55

    @Nupur Jain

     

    What the whole script does

    It checks whether the subscriber’s email address exists in the exclusion Data Extension. If ROWCOUNT(...) > 0, then the subscriber is found in the exclusion DE and should be excluded from the send.

     

    Breakdown of the components

    ComponentMeaning 

    LOOKUPROWS() | Searches a Data Extension for rows that match a specific field and value. Returns all matching rows. 

    "Exclusion_DATA_EXTENSION_NAME" | The name of the Data Extension being checked. This is where exclusion records are stored. 

    "EMAIL_ADDR_FIELD_NAME" | The column in the Data Extension to compare (e.g., EmailAddress). 

    EMAILADDR | The value being checked — usually the subscriber's email sent in the context of a send. 

    ROWCOUNT() | Counts how many rows the LOOKUPROWS function returned. 

    > 0 | Checks if the count is greater than zero (meaning at least one match exists).

0/9000

Hello everyone, 

 

I'm currently developing a solution to programmatically create and manage journeys using the Journey Specification for [

https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/getting-started-spec.html

]. 

 

During development, I've run into a significant challenge: the official documentation for the Journey Specification appears to be incomplete. Many key attributes that exist in a journey's JSON payload, particularly within the activities array, are not defined or described in the available documentation. 

 

Specific Problems: 

 

  1. Missing Attributes: Numerous required and optional attributes are simply not mentioned. We are currently forced to reverse-engineer their purpose by inspecting the payload of existing journeys.
  2. Unclear Definitions: For the attributes that are documented, the specifications often lack crucial details such as data types, possible enum values, value ranges, or clear use-case descriptions.

 

This lack of comprehensive documentation makes our development process heavily reliant on trial and error, which is inefficient and raises concerns about the long-term stability and compatibility of our journeys with future platform updates. 

 

My Questions for the Community: 

 

  • Is there a more complete or detailed official documentation/API reference for the Journey Specification that I might have missed?
  • Has anyone in the community compiled any unofficial resources, notes, or guides that cover the full specification?
  • Specifically, could anyone provide insight into the structure and purpose of attributes like [e.g., a specific field within metaData or configurationArguments that you are struggling with]?

 

Any pointers to more comprehensive documentation would be greatly appreciated. 

 

Thank you! 

1 件の回答
0/9000