Knowledgebase

Sort by:
Issue Description You want to use Slack with webhooks to be able to customize the integration a bit more than using it as a Launchpoint service. Issue Resolution We will assume you have already created your App within the Slack API page  we will cover everything after that here. 1) Make sure you are logged in so you can access your App through the Slack API page. 2) Select your App: 3) From here you will want to select the "Incoming Webhooks" from underneath "Features": 4) Use the on/off toggle to the right of the title "Activate Incoming Webhooks" 5) Select the "Add New Webhook to Workspace" button to create a new URL that we will use for our webhook within Marketo: 6) Select where you want to post, either at a specific user or channel: 7) Now we are directed back to the page we were one, hit the copy button next to the Webhook URL to copy the URL as we will need it for a later step. 😎 Login to your Marketo instance and navigate to the Admin section. 9) Select Webhooks 10) Select Create Webhook. For the following fields assign the appropriate values: Webhook Name*        =        What ever you want to name Description                 =        A description of what the webhook is used for URL*                           =        Here is where we paste the URL we copied before Request Type*            =        POST Template                     =       This is the information you want to send to your slack channel/user It should in the following format:                                              payload={"text": "DEVELOPER SITE ALERT: {{lead.First Name:default=edit me}} {{lead.Company:default=edit me}},                                                            {{lead.Email Address:default=no email address}}" } Request Encoding Token     =  None (You can change this if you want) Response Type                    =  None 11) Click create and now we are ready to call our webhook and send necessary data to our users in Slack! Who This Solution Applies To Slack Users
View full article
Issue Description Facebook Lead Ads was configured in a Sandbox subscription and then migrated to the Production subscription after testing was completed. After that swap, the Facebook Lead Ads integration is not passing records to the Production subscription.     Issue Resolution Deleting the Facebook LaunchPoint service does not unregister it from the Facebook Lead Ad pages. To ensure that the Facebook Lead Ad pages is unregistered from the Sandbox subscription and successfully reconnects to the production subscription, perform the following steps:       1. Go into the sandbox and create (or Edit if it still exists) the Facebook LaunchPoint again (just leave the default settings for pages and fields).   2. Once created, go back into the Facebook LaunchPoint and UNSELECT all of the pages that are currently selected (You want to make sure no pages are selected at this point).   3. Save. By doing this you will be unregistering the Marketo endpoint from all the Facebook Lead Ad pages for the sandbox subscription. You can then delete the LaunchPoint if you wish from the Sandbox subscription.   4. Go into the production subscription, since the Facebook LaunchPoint service exists, go back in edit mode and select all the pages you want to leads to come from.   5. Save. This should be able to successfully select the Facebook Lead Ad pages and register them to the production subscription.   6. Test one of the Facebook Lead Ad pages and verify if the data syncs to the Production subscription.     Who This Solution Applies To Facebook Lead Ads Is this article helpful ? YesNo
View full article
Issue Description You receive the following notification: The user you have authorized for you Facebook Lead Ads Launchpoint Service may have Insufficient Permissions. Issue Resolution Visit the Facebook help center to validate that the authorized user has all administrative permissions to both your company page and advertising account. If authorized user has all administrative permissions, please contact Marketo Support for further investigation Who This Solution Applies To Customer who use Facebook Lead Ad service
View full article
Issue Description When attempting to publish a landing page to Facebook, you get the error "Error when calling Social Campaign API. Warnings: Error while creating facebook tab."   Issue Resolution If you haven't purchased Ad Targeting add-on for your instance, you could face this issue. You can contact your Customer Success Manager to include this add-on in your Marketo subscription.  If you are facing the issue in spite of having ad targeting add on to your subscription, we would suggest that you contact Marketo support and we will be able to troubleshoot it for you.     Is this article helpful ? YesNo
View full article
Issue Description You are receiving this error from your GoToWebinar Launchpoint Service: API Error: Authentication succeeded, but access to the requested resource is denied. This error can occur either in Launchpoint Tab's Service details in Admin or when trying to Refresh an Event Program and selecting the service in the drop down menu. Issue Resolution This error "API Error: Authentication succeeded, but access to the requested resource is denied." is a response from GoToWebinar when Marketo sends an API Call to retrieve the Webinar Meeting details. What is the main cause of this? This is mainly a licensing issue with the Account Credentials specified in the Launchpoint service. The GoToWebinar account does not have a GoToWebinar License and therefore, the account has successfully "Authenticated" and the Requested resource (GoToWebinar Meeting Details) were denied as it does not have access to GoToWebinar features. How to check if you have a license? Login into the home page of GoToWebinar with the account credentials used in the Launchpoint Service and check if GoToWebinar Product is selectable. (if GTW is not selectable then the account does not have a product license) Speak to your GoToWebinar Account Admin if you are using a corporate account and ensure that it has a GoToWebinar License. Contact the GoToWebinar's Support Team Other Causes Other reasons this may have occurred is that a Trial account for GoToWebinar was used and the trial has expired. You may be using a login under a corporate account that does not have the license or was removed. - Check with your GoToWebinar Admin for more details Who This Solution Applies To GoToWebinar Launchpoint Users Is this article helpful ? YesNo
View full article
Issue Description What type of formats are accepted for uploading data to Facebook custom audiences from Marketo? Issue Resolution Note: The phone numbers must always have the country code included even if they are in the same country as your business.. The endpoint for facebook allows the following formats: 1-234-567-8910 12345678910 +44 123 456 7890 With or without punctuation is allowed.       Is this article helpful ? YesNo
View full article
Issue Description Do webhook calls contribute to the daily API limit/quota visible in [Admin > Integration > Web Services > API Call Information] ? Issue Resolution No, webhook calls are not counted as part of the daily API limit. Webhooks do not have any execution limits.
View full article
Issue Description The GoToWebinar service in Admin > Launchpoint shows a Failed API Error - API Error: ERROR -> HTTP Code = '403' Issue Resolution This error occurs due to an issue with the credentials Marketo uses to access the GoToWebinar service. To fix this, you would need to re-login to the GoToWebinar service under Admin > Launchpoint.  Once this is done, the error should be resolved.  You should also check the program membership for the webinar programs in Marketo, since any leads who attempted to register for a webinar while the error was in effect will have a status of "Registration Error" and will need to have their status corrected to "Registered." Who This Solution Applies To Customers integrated with GoToWebinar
View full article
Issue Description Is it possible to integrate multiple social media accounts with Marketo? Issue Resolution There is  only one LaunchPoint service for each, but multiple accounts can be referenced in : Lead gen forms - Linkedln Custom audiences - Facebook
View full article
Issue Description Change SFDC Campaign Status, Add to SFDC Campaign, and Sync Lead to SFDC Campaign flow steps are skipped/failed when the SFDC Campaign is synced with a Marketo Program. You may see " "Skipped execution due to that the SFDC campaign was linked with a program." Issue Resolution When the Marketo Program is synced with the SFDC Campaign, Marketo Program Membership will automatically sync over status updates to Salesforce. This automatic process overrides the all SFDC Campaign-related and Sync-related flow steps and will cause them to be skipped/fail in Smart Campaigns. Who This Solution Applies To Clients integrated with Salesforce, and t hose who sync SFDC Campaigns with Marketo Programs. Is this article helpful ? YesNo
View full article
Issue Description When you are entering the names of Facebook Forms into Marketo Triggers, Filters, and/or other fields, Marketo may present an error (red-squiggle) under the name value, stating that the value is invalid.   Issue Resolution The reason that Marketo states this value is invalid is because the Facebook Form has not yet been filled out for the first time. Only after an existing Marketo Record has filled out the Facebook Form will the Name Value of the form be in the Marketo system.   If you were interested in setting up a Trigger Campaign to trigger off Facebook Form fillouts, you would first have to fill out the form with a test record that exists in the Marketo Lead Database. If the situation was within a Batch Campaign, or entering the Form Name in any other fields, the same resolution would apply: fill out the form with a test record that you are associated with in the Marketo Lead Database. Is this article helpful ? YesNo
View full article
Issue Description You see the following error when trying to refresh data using API for the webinar provider (GoToWebinar): "FailedAPI Error: Authentication succeeded, but access to the requested resource is denied." Issue Resolution Check LaunchPoint to see if the integration between Marketo and GTW is broken. Go to Admin > LaunchPoint to see the integration between GTW and Marketo. If you see the error "FailedAPI Error: Authentication succeeded, but access to the requested resource is denied," this is a permission issue with GTW. C heck with GTW Support to see why requesting resource is being denied. Who This Solution Applies To All the customers/clients who use GTW as an integration with Marketo.
View full article
As part of the September 2012 release, Marketo exposed the ability to create a Webhook.  Webhooks are essentially HTTP callbacks that allow you to send a "payload" (i.e. xml, json) to a URL and include parameters. Here is a walk-through on how to create a Webhook that sends an SMS Message to a Marketo Lead using the Twilio messaging platform. Step 1 Sign up for a Twilio Account (www.twilio.com).  Be sure to follow the instructions on validating any numbers that will be used to send an SMS message. Step 2 Navigate to Admin in your Marketo Account Step 3 Select Treasure Chest from the left tree and click Edit in the Webhooks section Step 4 Check the box to Enable Webhooks Step 5 In the Admin menu, select  Webhook and click New Webhook Step 6 Enter the Webhook details as defined in the below screenshot.  A powerful feature of Webhooks is that you can include Tokens as part of the URL and/or Message for further customization. Note:  You will replace the [ACCOUNT_SID] & [AUTH_TOKEN] values with what is specified in your Twilio account. Step 7 Create a Program/Campaign in Marketo.  In the example below, a Program/Campaign was created with associated LandingPage/Form to send out an SMS text message when the lead fills out form. Step 8 See the activity appear in the Activity Tab for that lead in Marketo Step 9 Check SMS activity in your Twilio Account Log
View full article