# Link Tracking: Connector Types

In link tracking, you can use rules to control what happens to links based on the types of connectors (read more [here](https://docs.messagebird.com/taxi/Feeds%20\&%20Link%20Tracking/Link%20Tracking/link-tracking-manager-href-settings)).

\
You have to target the connector type in these rules which can be found below:

Acoustic = SP\_MAILING\_TEMPLATE

Adobe Campaign API Export = NEOLANE

Adobe Campaign File Export = NEOLANE\_FILE

Amazon SES = AWS\_SES

AWS S3 Connector = AWS\_S3

Braze, type = BRAZE

Bronto = BRONTO

BlueShift Connector = BLUESHIFT

Campaign Monitor = CM

Dotdigital = DM

Epsilon = EPSILON

Emarsys = EMARSYS

Eloqua = ELOQUA

Episerver Transactional Mail Connector = EPISERVER\_TRANSACTIONAL

Episerver Smart Campaign Connector = EPISERVER\_CAMPAIGN

Hubspot = HUBSPOT

Iterable = ITERABLE

Klaviyo = KLAVIYO

Mailchimp = M\_CHIMP

Messagebird = MessageBird

Marketo = MARKETO

Oracle Marketing Cloud (RPL) = RSRPL

Optimove = OPTIMOVE

Omeda = OMEDA

Pardot Salesforce Classic = PARDOT

Pardot Salesforce OAuth = PARDOT\_OAUTH

Pardot Salesforce Handlebars = PARDOT\_HANDLEBARS

Sendgrid Campaign = SENDGRID\_CAMPAIGN

Sendgrid Marketing = SENDGRID\_MARKETING

Sendgrid Transactional = SENDGRID\_TRANSACTIONAL

Sendgrid Design Library = SENDGRID\_DESIGN\_LIBRARY

Salesforce Marketing Cloud Content Builder = SFMC\_CONTENT\_BUILDER

Salesforce Marketing Cloud - Classic content = ET

Sailthru Campaign Export = SAILTHRU\_API

Sailthru Template Export = SAILTHRU\_TEMPLATES\_API

Sparkpost = SPKPOST

SAP Connector = SAP

Yes Marketing Connector = YESMAIL


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/taxi/feeds-and-amp-link-tracking/link-tracking/link-tracking-connector-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.