Skip to content

Commit 28620a9

Browse files
bot-docsteambot-docsteam
authored
Merge pull request #669 from segmentio/repo-sync
repo sync
2 parents ceae962 + acab43d commit 28620a9

File tree

9 files changed

+1560
-255
lines changed

9 files changed

+1560
-255
lines changed

‎src/_data/catalog/destinations.yml

Lines changed: 1418 additions & 251 deletions
Large diffs are not rendered by default.

‎src/_data/catalog/regional-supported.yml

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2244,6 +2244,22 @@ destinations:
22442244
endpoints:
22452245
- us
22462246
- eu
2247+
- id: 632b1116e0cb83902f3fd717
2248+
display_name: HubSpot Cloud Mode (Actions)
2249+
slug: hubspot-cloud-mode-actions
2250+
url: connections/destinations/catalog/hubspot-cloud-mode-actions
2251+
regions:
2252+
- us
2253+
endpoints:
2254+
- us
2255+
- id: 631a1c2bfdce36a23f0a14ec
2256+
display_name: HubSpot Web (Actions)
2257+
slug: hubspot-web-actions
2258+
url: connections/destinations/catalog/hubspot-web-actions
2259+
regions:
2260+
- us
2261+
endpoints:
2262+
- us
22472263
- id: 5728ed9c80412f644ff132d9
22482264
display_name: Hull
22492265
slug: hull
@@ -2575,6 +2591,14 @@ destinations:
25752591
- eu
25762592
endpoints:
25772593
- us
2594+
- id: 62f435d1d311567bd5bf0e8d
2595+
display_name: LinkedIn Audiences
2596+
slug: linkedin-audiences
2597+
url: connections/destinations/catalog/linkedin-audiences
2598+
regions:
2599+
- us
2600+
endpoints:
2601+
- us
25782602
- id: 59526b3170a3e552b957552b
25792603
display_name: LinkedIn Insight Tag
25802604
slug: linkedin-insight-tag

‎src/connections/destinations/catalog/actions-hubspot-cloud/index.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
title: HubSpot Cloud Mode (Actions) Destination
33
hide-boilerplate: true
44
hide-dossier: false
5-
hidden: true
6-
private: true
75
id: 632b1116e0cb83902f3fd717
86
versions:
97
- name: 'HubSpot Web (Actions)'
@@ -55,4 +53,7 @@ HubSpot Cloud Mode (Actions) provides the following benefits over the classic Hu
5553
Segment provides prebuilt mappings for contacts and companies. If there are other standard objects you would like to create records in, please use the **Create Custom Object Record** action. For example, to create a deal in HubSpot, add a mapping for Create Custom Object Record, set up your Event Trigger criteria, and input a literal string of "deals" as the Object Type. You can use the Properties object to add fields that are in the [deals object](https://developers.hubspot.com/docs/api/crm/deals){:target="_blank"}, such as `dealname` and `dealstage`. The same can be done with other object types (for example, tickets, quotes, etc). Please note, Segment only supports creating new records in these cases; updates to existing records are only supported for contacts and companies.
5654

5755
### Why aren't my custom behavioral events appearing in HubSpot?
58-
HubSpot has several limits for custom behavioral events, including a limit on the number of event properties per event. Each event can contain data for up to 50 properties. If this limit is exceeded, the request will fail. See [HubSpot documentation](https://knowledge.hubspot.com/analytics-tools/create-custom-behavioral-events#define-the-api-call){:target="_blank"} for other limits.
56+
HubSpot has several limits for custom behavioral events, including a limit on the number of event properties per event. Each event can contain data for up to 50 properties. If this limit is exceeded, the request will fail. See [HubSpot documentation](https://knowledge.hubspot.com/analytics-tools/create-custom-behavioral-events#define-the-api-call){:target="_blank"} for other limits.
57+
58+
### Does the HubSpot Cloud Mode (Actions) destination support EU data residency?
59+
Yes. HubSpot will automatically redirect API requests directly to an EU data center if your HubSpot instance is on an EU data center. See more in HubSpot's [Routing API Traffic](https://product.hubspot.com/blog/routing-api-traffic){:target="_blank"} article.

‎src/connections/destinations/catalog/actions-linkedin-audiences/index.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: LinkedIn Audiences Destination
3+
hide-personas-partial: true
4+
hide-boilerplate: true
5+
hide-dossier: false
6+
id: 62f435d1d311567bd5bf0e8d
7+
---
8+
9+
LinkedIn Audiences enables advertisers to send Segment Engage Audiences to LinkedIn as Matched Audiences using [LinkedIn's API](https://learn.microsoft.com/en-us/linkedin/marketing/integrations/matched-audiences/matched-audiences){:target="_blank"}.
10+
11+
By using Segment's Engage Audiences with LinkedIn, you can increase traffic and drive conversions with hyper-relevant ads that promote product discovery.
12+
13+
> info ""
14+
> The LinkedIn Audiences destination is in beta and is in active development. Some functionality may change before it becomes generally available.
15+
16+
## Getting Started
17+
18+
Before connecting to the LinkedIn Audiences destination, you must have a [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager){:target="_blank"} account and an Ad Account ID. In addition, the user authenticating with LinkedIn must have one of the following LinkedIn ad account roles: `ACCOUNT_BILLING_ADMIN`, `ACCOUNT_MANAGER`, `CAMPAIGN_MANAGER`, or `CREATIVE_MANAGER`.
19+
20+
To add the LinkedIn Audiences destination:
21+
22+
1. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with LinkedIn Audiences. Either choose an existing Engage Audience or create a new one. This is the Audience you plan to send to LinkedIn.
23+
24+
2. Within the Audience, click **Settings** and copy the Audience Key. You'll need this key later.
25+
26+
3. Navigate to **Engage > Engage Settings** and click **Destinations**. Please ensure you are still in the correct Engage space.
27+
28+
4. Search for “LinkedIn Audiences” and select the destination.
29+
30+
5. Click **Configure LinkedIn Audiences**.
31+
32+
6. On the Select Source screen, your Engage space should already be selected as the source. Click **Confirm Source**.
33+
34+
7. On the Destination **Settings** tab, name your destination and authenticate with LinkedIn using OAuth.
35+
36+
8. Once authenticated, input your LinkedIn Ad Account ID from your [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager){:target="_blank"} account. Toggle “Enable Destination” on and click **Save Changes**.
37+
38+
9. Navigate to the **Mappings** tab, click **New Mapping**, and select **Sync To LinkedIn DMP Segment**.
39+
40+
10. Under Select mappings, input the Audience Key you copied in Step 2 as the “Segment Engage Audience Key.” Do not change any other defaults. Click **Save** and toggle to enable the mapping.
41+
* **Note:** The Audience Key must be manually entered to ensure users in the Engage Audience are sent to the correct DMP Segment in LinkedIn. For every Engage Audience you want to send to your LinkedIn Ads Account, a separate **Sync To LinkedIn DMP Segment** mapping must be created. You can create up to 50 mappings within an instance of the LinkedIn Audiences destination.
42+
43+
11. Navigate back to **Engage > Audiences** and click on the Audience from Step 1.
44+
45+
12. Click **Add Destinations** and select the LinkedIn Audiences destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and disable **Send Identify**. Click **Save Settings**.
46+
47+
![engage audience destination settings](images/image1.png)
48+
49+
The setup is complete and the Audience will start syncing to LinkedIn. Segment automatically creates a new DMP Segment in LinkedIn and will add or remove users accordingly. The Audience appears in your [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager){:target="_blank"}, account under **Plan > Audiences > Matched**.
50+
51+
To sync additional Audiences from your Engage space, create a separate mapping in the LinkedIn Audiences destination. Navigate to **Connections > Destinations**, search and select the LinkedIn Audiences destination, and follow Steps 9-11 above.
52+
53+
{% include components/actions-fields.html settings="true"%}
54+
55+
## Troubleshooting
56+
57+
### Access & Refresh Tokens
58+
LinkedIn's OAuth access tokens have a time to live (TTL) of 60 days; refresh tokens have a TTL of one year. Segment automatically updates your access token as long as your refresh token is valid. You won't see any errors or interruptions in data delivery if your access token expires while your refresh token is valid.
59+
60+
Upon expiry or revocation of a refresh token, you'll see `Refresh Token Expired` errors in the Delivery Issues section of your LinkedIn Audiences destination **Event Delivery** tab.
61+
62+
Unknown errors from LinkedIn related to OAuth appear as `Oauth Refresh Failed`.
63+
64+
To remedy either error, please navigate to the **Settings** tab of your LinkedIn Audiences destination and select **Reauthorize** under the Connection heading and complete the OAuth flow.

‎src/connections/destinations/catalog/atatus/index.md

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,31 @@
11
---
22
title: 'Atatus Destination'
3-
hidden: true
43
id: 54c02204db31d978f14a7f6d
54
---
5+
6+
[Atatus](https://www.atatus.com/) provides visibility into the performance of an application and its underlying infrastructure under a single dashboard. This visibility can help businesses identify and diagnose issues, and take corrective action to prevent or resolve application issues.
7+
8+
## Getting Started
9+
Before you start, make sure Atatus supports the source type and connection mode you’ve chosen to implement. You can learn more about [connection modes here](/docs/connections/destinations/#connection-modes).
10+
11+
1. From the destinations catalog page in the segment web app, click on **Destinations -> Add Destination**.
12+
2. Search for "Atatus" in the destination catalog and select Atatus as the destination.
13+
3. Click on **Configure Atatus**.
14+
4. Choose which **Data Source** should send data to the Atatus destination and click Next.
15+
5. Enter the desired destination and click Save. You will be navigated to the settings page where
16+
you will have to add the API key to start receiving insights.
17+
6. You can find the API key in your browser project settings.
18+
7. Enter the **API Key** in the Atatus destination settings in Segment.
19+
20+
## Supported Methods
21+
22+
### Identify
23+
If you’re not familiar with the Segment Specs, take a look to understand what the [Identify](https://segment.com/docs/connections/spec/identify/) method does. An example call would look like this:
24+
25+
```javascript
26+
analytics.identify('userid_123', {
27+
name: "John Doe",
28+
email: "johndoe@example.com"
29+
});
30+
```
31+
When you call `identify()` method, the Atatus SDK call `atatus.setUser` by passing in the traits you provided. Atatus will map the userId you provide as traits.id with which you can easily track user activity and gain a specific user's performance insights.

‎src/connections/destinations/catalog/hubspot-cloud-mode-actions/index.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: 'HubSpot Cloud Mode (Actions) Destination'
3+
hidden: true
4+
id: 632b1116e0cb83902f3fd717
5+
published: false
6+
beta: true
7+
---

‎src/connections/destinations/catalog/hubspot-web-actions/index.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: 'HubSpot Web (Actions) Destination'
3+
hidden: true
4+
id: 631a1c2bfdce36a23f0a14ec
5+
published: false
6+
beta: true
7+
---

‎src/connections/destinations/catalog/linkedin-audiences/index.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: 'LinkedIn Audiences Destination'
3+
hidden: true
4+
id: 62f435d1d311567bd5bf0e8d
5+
published: false
6+
beta: true
7+
---

‎src/profiles/profile-api-limits.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
title: Profiles Limits
33
plan: profiles
4+
redirect_from:
5+
- '/profiles/product-limits'
46
---
57

68
## Profile API

0 commit comments

Comments
 (0)