Marketing-Cloud-Consultant Sample Questions Answers

GTL (Guide Template Language) is a scripting language that allows parsing and displaying JSON or XML data within an email. GTL can be used to make API calls to external services, such as the Sunny Sky API, and display the response within the email. For example, NTO can use the HTTPGet() AMPscript function to retrieve the weather information from the Sunny Sky API as a JSON object, and then use the TreatAsContent() AMPscript function to parse and display the JSON object using GTL tags and variables. References: https://help.salesforce.com/articleView?id=sf.mc_es_guide_template_language.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_httpget_ampscript_function.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_treatascontent_ampscript_function.htm &type=5

Two considerations that should be made when using a File Drop Automation are:

• They may utilize an external FTP site. A File Drop Automation can be configured to use an external SFTP location as well as an Enhanced FTP location for file triggers.
• The directory is unable to be used by another File Drop Automation. A File Drop Automation can only use one directory for file triggers, and that directory cannot be used by another File Drop Automation.

The directory used by the file trigger can be inside or outside the import directory, as long as it is not used by another File Drop Automation. The directory can contain more than five file triggers, but only one file trigger can start an automation at any given time. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_file_drop_automation_studio_triggers.htm &type=5

To capture customer feedback via email and create a new case in Service Cloud if a customer indicates they are unhappy with the service they have received, Northern Trail Outfitters should use an Engagement Split to capture positive or negative responses, and a Case Activity to create a new case in Service Cloud. An Engagement Split is an activity that allows marketers to route contacts based on their engagement with email messages, such as opens or clicks. A Case Activity is an activity that allows marketers to create cases in Service Cloud based on contact attributes or journey data. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_engagement_split.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_case_activity.htm &type=5

To select an audience of subscribers who have made purchases in the last 6 months, but are yet to be loyalty members, Northern Trail Outfitters should use Contact Builder Attribute Groups. Attribute Groups are collections of data extensions and data sources that are linked by common fields or attributes. Attribute Groups allow marketers to create segments and filters based on data from multiple sources, such as purchase data and loyalty data. References: https://help.salesforce.com/s/articleView?id=sf.mc_cab_attribute_groups.htm &type=5

Two options that would prevent the customer from duplicating records when implementing a Sales Cloud instance are:

• Get existing records updated with new Keys sourced from Sales Cloud instance. This option will allow the customer to update their existing records in Marketing Cloud with new keys that match their Sales Cloud records, such as Contact ID or Lead ID. This will ensure data consistency and avoid duplication across both systems.
• Continue as normal, as Marketing Cloud Contact Models will dedupe keys by Email Address. This option will allow the customer to continue using Email Address as their primary key in Marketing Cloud, and rely on Marketing Cloud Contact Models to dedupe keys by Email Address when syncing data from Sales Cloud. This will ensure data accuracy and avoid duplication within Marketing Cloud.

Uploading CSV with Migrated Subscriber Keys to All Subscribers will not prevent duplication, as it will create new records in Marketing Cloud with different keys than the existing records. Purging the current records and carrying on with new keys sourced from Sales Cloud will result in data loss and potential compliance issues. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_contact_key.htm &type=5

Two actions that would successfully write send time variables to their Send Log are:

• Match an AMPscript variable name to a Send Log field. This action will allow the customer to write the value of an AMPscript variable to a corresponding field in the Send Log data extension. For example, if the customer has a Send Log field named ProductName and an AMPscript variable named @ProductName, then the value of @ProductName will be written to the ProductName field in the Send Log.
• Use the WriteToLog() AMPscript function in the content. This action will allow the customer to write one or more values to a specified field in the Send Log data extension using an AMPscript function. For example, if the customer wants to write the value of @ProductName and @ProductPrice to the ProductInfo field in the Send Log, they can use WriteToLog(“ProductInfo”,@ProductName,@ProductPrice) in their content.

Ensuring the send log is linked in an attribute group is not necessary for writing send time variables to their Send Log, as it is only used for creating relationships between data sources in Contact Builder. Enabling send logging to a data extension during send process is not an action that would write send time variables to their Send Log, as it is only a setting that enables or disables send logging for a specific email send. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_create_a_sendlog_data_extension.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_write_to_the_send_log.htm &type=5

To send an auto-reply message using a pre-defined HTML email when subscribers reply to an email, Northern Trail Outfitters should create a triggered send and from a sender profile properties page, enable ‘Custom Reply Mail Management Settings’, ‘Use Auto Reply’ and ‘Reply using triggered send’ options, then select the triggered send email. This will allow them to use a custom HTML email as an auto-reply message instead of a plain text message. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_reply_mail_management.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_create_a_triggered_email_message.htm &type=5

Two considerations that should be made about tokenized sending are:

• Personalization strings still allow PII to be displayed within an email. Tokenized sending does not encrypt or mask PII within an email, it only prevents it from being stored in Marketing Cloud. Therefore, personalization strings should be used with caution and only when necessary.
• Service Level Agreements for email sends are unsupported with the inclusion of outside servers. Tokenized sending relies on an external server to provide PII at send time, which may introduce latency or errors that affect the delivery time and performance of emails.

Journey Builder decision splits do not provide a method to access tokenized data natively, but they can be configured with custom activities or API calls to do so. Tokenized sending does not require field-level data encryption for additional security, as PII is never stored in Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_tokenized_sending.htm &type=5

Two options that could be recommended for localizing email content to speak to subscribers in their own language are:

• Leverage AMPscript within an email template to lookup subscriber language and personalize the email based on the value. AMPscript is a scripting language that allows marketers to perform complex tasks within messages, such as looking up data from data extensions, applying conditional logic, or displaying dynamic content based on subscriber attributes or behaviors.
• Leverage enhanced dynamic content blocks within Content Builder to create language-specific emails. Enhanced dynamic content blocks are blocks that allow marketers to create personalized content based on rules and filters without coding.

Leveraging personalization strings within the email template will not help with localization, as they are used for inserting simple subscriber attributes or system information into messages. Leveraging Content Builder to create email templates for each individual language will not be efficient or scalable, as it will require creating and maintaining multiple templates for each message. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_ampscript_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_ceb_enhanced_dynamic_content_blocks.htm &type=5

The Deployment Manager extension product can be used to speed up the migration of data extensions and Journey Builder configurations between each environment. The Deployment Manager allows users to create packages of Marketing Cloud assets and deploy them across different business units or accounts. The Deployment Manager supports data extensions and journeys as well as other assets such as emails, templates, automations, and content blocks. References: https://help.salesforce.com/s/articleView?id=sf.mc_de_deployment_manager.htm &type=5

A journey with CRM date based entry source can be used to trigger emails based on a date field in the CRM object, such as the reminder date. The journey can also use the Update Contact activity to update the record in CRM after sending the reminder email. References: https://help.salesforce.com/articleView?id=sf.mc_jb_date_based_events.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_update_contact.htm &type=5

To get real-time updates on transactional email metrics, such as Sent and Not Sent, Northern Trail Outfitters should use Event Notification Service. Event Notification Service is a feature that allows marketers to receive real-time notifications of email tracking events via webhooks or APIs. Event Notification Service can help marketers monitor and troubleshoot transactional email sends and ensure compliance with legal obligations. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_event_notification_service.htm &type=5

A contact is a person who interacts with a brand across one or more channels, such as email, mobile, web, etc. A contact is identified by a contact key, which is usually the same as the subscriber key in Marketing Cloud or the contact or lead ID in Sales Cloud. When users register with the mobile app, they will create new contacts in Marketing Cloud with their device IDs as contact keys. However, these contacts will not be associated with their contact keys in Sales Cloud until they are synchronized through Marketing Cloud Connect, which can take up to 24 hours. Therefore, newly registered users will create additional contacts in Marketing Cloud until they are matched with their existing contacts in Sales Cloud. References: https://help.salesforce.com/articleView?id=sf.mc_co_what_is_a_contact.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implementing_contacts_in_the_marketing_cloud.htm &type=5

Synchronized data extensions are data extensions that are automatically populated with data from Sales Cloud objects using Marketing Cloud Connect. They can be configured with filters to limit the records that are imported based on criteria such as field values or record types. By using synchronized data extensions with a filter on the consent checkbox field, NTO can import their Sales Cloud data into Marketing Cloud and leverage it within Journey Builder. Synchronized data extensions can be refreshed as frequently as every 15 minutes, which meets the requirement of having no more than 30 minutes delay. References: https://help.salesforce.com/articleView?id=sf.mc_co_data_integration_synchronized_data_sources.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implement_synchronized_data_sources_best_practices.htm &type=5

To inject customers into journey B based on email engagement in journey A, Northern Trail Outfitters should use an engagement split followed by a contact activity in journey A. The engagement split can evaluate if customers opened or clicked the email in journey A. The contact activity can update a boolean field on an engagement data extension that indicates if customers are eligible for journey B. Then, an automation can run a query activity to select the customers who have the boolean field set to true and inject them into journey B. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_engagement_split.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_contact_activity.htm &type=5

 To integrate Marketing Cloud with their existing point-of-sale system in order to email purchase receipts to their customers, Northern Trail Outfitters should use MuleSoft Anypoint Platform. MuleSoft Anypoint Platform is a tool that allows marketers to connect and integrate different systems and applications using APIs and connectors. MuleSoft Anypoint Platform can help transform and map data between different formats and protocols, such as JSON and SOAP.

References: https://www.mulesoft.com/platform/anypoint-platform

An entry source filter is a filter that can be applied to an entry source in journey builder to limit which contacts are injected into a journey based on criteria such as field values or record types. A decision split is a journey builder activity that allows branching the journey based on attribute values or engagement behavior of each contact. By using an entry source filter on their order data extension, NTO can filter contacts whose status has changed to ‘shipped’ that day and inject them into their journey. By using a decision split within their journey, they can further segment contacts based on other criteria such as purchase amount or product category. References: https://help.salesforce.com/articleView?id=sf.mc_jb_entry_source_filter.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_decision_split.htm &type=5

The Contact ID field name should be included in the report in addition to email address when using a Send Flow in Content Builder. The Contact ID is a unique identifier for each contact in Sales Cloud and Marketing Cloud. It is required for sending emails to contacts using a Send Flow. The other field names are not required for this purpose. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_send_flow.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_contact_id.htm &type=5

Creating an installed package in Marketing Cloud with Read and Write permissions for data extensions should be used to facilitate the functionality of upserting rows into a data extension using a REST API endpoint. An installed package is a container for one or more API integrations that provides authentication credentials and permissions for accessing Marketing Cloud resources. Read and Write permissions for data extensions allow the API integration to retrieve and modify data in data extensions. References: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/create_a_package.html https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/data-extensions.html

The _Subscribers data view contains information about each subscriber in an account, such as subscriber key, email address, status, and business unit ID. The _BusinessUnitUnsubscribes data view contains information about each unsubscribe event for each subscriber in a business unit, such as subscriber key, business unit ID, and unsubscribe date. By using these two data views, the data team can find subscribers in their Marketing Cloud account and their unsubscribe data for child business units. References: https://help.salesforce.com/articleView?id=sf.mc_as_data_view_subscribers.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_as_data_view_businessunitunsubscribes.htm &type=5

A Verification Activity can be used to prevent emails from being sent if they exceed a certain number of contacts. A Verification Activity checks the number of records in a data extension or list and stops the automation if the number is above or below a specified threshold. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_verification_activity.htm &type=5

To query Marketing Cloud for send data across SMS, Push, and email, Northern Trail Outfitters should use _Send Data Views. Data Views are system-generated tables that store tracking and system data for different channels and platforms in Marketing Cloud. _Send Data Views contain information about email sends, SMS sends, and push sends across different business units and accounts. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_send.htm &type=5

To utilize a Retention Policy for a data extension that stores web behavior data, two methods are possible. One is to delete data from the data extension prior to twelve months ago, then configure a Retention Period via Contact Builder. This will allow the data extension to keep only the data from the previous twelve months and delete any older data automatically. The other method is to replace the current data extension with a new data extension configured with a Retention Period. This will create a new data extension with the same fields and settings as the old one, but with a Retention Period enabled. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_data_retention_policies.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_create_a_new_data_extension_from_an_existing_data_extension.htm &type=5

The _ListSubscribers data view contains information about subscribers who belong to a specific list, including publication lists. It can be used to query subscribers based on their list ID, status, and date joined or unsubscribed. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_listsubscribers.htm &type=5

To recommend a scalable business unit hierarchy for Northern Trail Outfitters and its three subsidiaries, the consultant should suggest one parent BU and three child BUs with their own Sender Authentication Packages. This will allow each subsidiary business to have their own branding, content, and subscribers, as well as access to aggregate reporting and shared subscribers from the parent BU. Each child BU should have its own Sender Authentication Package to authenticate its email sends with its own domain and branding. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_business_unit_setup.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

To know the number of contacts in their account and email it to their Chief Marketing Officer on a weekly basis, Northern Trail Outfitters should schedule the Contacts Counts Standard Report. This report shows how many contacts are in Marketing Cloud across different channels and platforms. The report can be scheduled to run at a recurring interval and emailed to one or more recipients. References: https://help.salesforce.com/s/articleView?id=sf.mc_rn_contacts_count_report.htm &type=5

MobileConnect Demographics is a data source that is supported to personalize SMS messages. MobileConnect Demographics is a system-generated attribute group that contains information about mobile subscribers, such as phone number, locale, status, keyword, and source. This information can be used to insert personalization strings or AMPscript variables into SMS messages. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_mobileconnect_demographics.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_personalize_an_sms_message.htm &type=5

Two potential reasons for SMS responses getting the default keyword response rather than the appropriate next keyword response are:

• Responses are not sent within the Conversation Window. The Conversation Window is a setting that defines how long MobileConnect waits for a response from a subscriber after sending an outbound message. If a subscriber responds after the Conversation Window expires, MobileConnect treats their response as a new inbound message rather than part of an ongoing conversation.
• Next keyword was not specified on the outbound message. The Next Keyword is a setting that defines what keyword MobileConnect expects from a subscriber after sending an outbound message. If a subscriber responds with a different keyword than what MobileConnect expects, MobileConnect treats their response as a new inbound message rather than part of an ongoing conversation.

Responses containing “stop” in the message content will not get the default keyword response, but rather an opt-out confirmation message. Responses sent with AMPscript in body will not affect how MobileConnect handles responses, as AMPscript is only evaluated at send time. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_conversation_window.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_next_keyword.htm &type=5

To format the JSON payload from their commerce platform within the email, Northern Trail Outfitters should use the BuildRowSetFromJSON() AMPscript function. The BuildRowSetFromJSON() AMPscript function is a function that allows marketers to parse a JSON string and return a rowset object that can be used to display data within an email message. The BuildRowSetFromJSON() AMPscript function can handle nested JSON objects and arrays. References: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic-content.meta/mc-programmatic-content/buildrowsetfromjson.htm

To send SMS messages to contacts located in the United States using a Salesforce entry event in a journey, NTO should format the phone field in Salesforce as +l[phonenumber], where +1 is the country code for the United States and [phonenumber] is the 10-digit phone number without any spaces or dashes. This format ensures that Marketing Cloud can correctly identify and validate the mobile numbers for SMS sending. Normalizing phone numbers in journey settings only applies to mobile numbers stored in MobileConnect or MobilePush demographics tables, not to mobile numbers from Salesforce entry events. Selecting ‘US’ as the sending country in SMS activity only affects how opt-out keywords are processed, not how mobile numbers are validated. Configuring the phone field in Salesforce as US locale only affects how phone numbers are displayed in Salesforce, not how they are formatted for Marketing Cloud. References: https://help.salesforce.com/articleView?id=sf.mc_rn_june_2020_moc_normalize_phone_number_journey_setting.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_moc_country_code_processing_for_opt_out_keywords.htm &type=5 https://help.salesforce.com/articleView?id=admin_phoneformat.htm &type=5

This personalization string is used to direct a subscriber to a web version of the email, allowing them to view the email online even if their email client does not support HTML. For more information on personalization strings, please see the documentation here: https://help.salesforce.com/articleView?id=mc_es_personalization_strings.htm &type=5.

The %%view_email_url%% personalization string is a system-generated link that allows subscribers to view a web page version of an email. It can be included as the href attribute in a ‘view online’ link in an email template to enable users to view the email in a browser if they have trouble viewing it in their email client. The %%view_as_webpage%% personalization string is deprecated and should not be used. The %%vawp%% personalization string is an alias for %%view_as_webpage%% and should not be used either. The %%view_online%% personalization string does not exist. References: https://help.salesforce.com/articleView?id=sf.mc_es_view_email_url_personalization_string.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_view_as_web_page_personalization_string.htm &type=5

An auto-suppression list populated with the known email addresses can be used to ensure none of these competitors receive their emails. An auto-suppression list is a type of exclusion list that prevents subscribers from receiving certain types of messages based on criteria such as email address, subscriber key, or domain. References: https://help.salesforce.com/articleView?id=sf.mc_es_auto_suppression_lists.htm &type=5

To capture open-ended feedback from customers via SMS and write it to a data extension, Northern Trail Outfitters should use a text-response message template with embedded AMPscript to capture the response. A text-response message template is a template that allows marketers to send a text message to a mobile number and receive a reply. AMPscript is a scripting language that allows marketers to perform complex tasks within messages, such as inserting data into a data extension. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_text_response.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_ampscript_overview.htm &type=5

To report on ‘Not Sent’ contacts in Journey Builder, Northern Trail Outfitters should use the standard report ‘Subscribers Not Sent to’. This report shows how many contacts were not sent an email due to various reasons, such as unsubscribes, bounces, duplicates, or errors. References: https://help.salesforce.com/s/articleView?id=sf.mc_rn_subscribers_not_sent_to_report.htm &type=5

To troubleshoot the connection between Sales Cloud and Marketing Cloud, a consultant should start by validating Marketing Cloud and Sales Cloud permissions for the connecting users. The connecting users are the users who authenticated Marketing Cloud Connect in both systems. They need to have certain permissions and roles in both systems to enable full functionality of Marketing Cloud Connect. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_troubleshoot_marketing_cloud_connect_configuration_issues.htm &type=5

This setting allows the consultant to verify the sender's identity and configure the incoming email settings. Reference: https://help.salesforce.com/articleView?id=mc_es_sap_overview.htm &type=5

To redirect its emails to Marketing Cloud servers for processing, Northern Trail Outfitters should use a Sender Authentication Package. A Sender Authentication Package is a feature that allows marketers to authenticate their email sends with their own domain and branding, instead of using Marketing Cloud’s default domain and branding. This will improve email deliverability and reputation, as well as provide more control over email settings and preferences. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

Supporting inbound messages in each country would require additional long code implementation for MobileConnect. A long code is a standard phone number that can send and receive SMS messages. Each country has its own regulations and requirements for long codes, so a single long code cannot be used for all markets. The other functionalities do not tie to additional long code implementation. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_long_codes.htm &type=5

To use a simple segmentation strategy for identifying subscribers for their emails, Northern Trail Outfitters should use list model and groups in Single Send Journeys. List model is a method of storing subscriber information in lists rather than data extensions. Groups are segments of subscribers based on list attributes or behaviors. Single Send Journeys are journeys that allow marketers to send one-time messages to lists or groups using Journey Builder features. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_list_model.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_groups.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_single_send_journeys.htm &type=5

To use Case data from Service Cloud as part of their current email messaging campaign, Northern Trail Outfitters should use Synchronized Data Extensions on the Case Object with a Boolean filter on the Contact Me field. Synchronized Data Extensions are data extensions that allow marketers to sync data from Sales Cloud or Service Cloud objects into Marketing Cloud using filters and schedules. Using Synchronized Data Extensions on the Case Object with a Boolean filter on the Contact Me field will allow Northern Trail Outfitters to import cases that indicate the customer wants someone to contact them after the case is closed. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_synchronized_data_sources.htm &type=5

To send emails to loyalty members based on recent activity, a contact data entry source can be used to segment the data based on attributes and filters configured in Contact Builder. This allows for more flexibility and scalability than using a data extension entry source with an applied filter. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_sources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_attribute_groups.htm &type=5

To manually create a segment of both lead and contact records that can be targeted through the Send Flow in Content Builder, Northern Trail Outfitters should use a Salesforce Campaign. A Salesforce Campaign is an object in Sales Cloud that allows marketers to group leads or contacts for a specific marketing initiative, such as an email campaign. A Salesforce Campaign can be used as a target audience in Marketing Cloud using the Send Flow in Content Builder. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_send_flow.htm &type=5

To troubleshoot why tracking details from Email Studio initiated sends are not being sent back to Sales Cloud, Northern Trail Outfitters should verify that required profile attributes are properly mapped. Required profile attributes are attributes that are needed for Marketing Cloud Connect to function properly and sync data between Marketing Cloud and Sales Cloud. These attributes include Email Address, Subscriber Key, First Name, Last Name, and Full Name. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_troubleshoot_marketing_cloud_connect_configuration_issues.htm &type=5

SOAP API calls updating objects and CreateSalesforceObject() AMPscript are both types of API calls that are counted against the rolling 24-hour limit in Salesforce. Login calls and bulk API calls are not counted against this limit. References: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_api_concepts_limits.htm https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic-content.meta/mc-programmatic-content/createsalesforceobject.htm