Actions (Projects)

Campaign Registration and Phone Numbers

Q: How can I select a specific phone number or area code for my project?

A: During TCR registration, you can request specific phone numbers or area codes for your campaign. Once your registration successfully completes and the campaign is approved in our system, you will be able to retrieve your registered campaigns and associated phone numbers through the API.

Use the following endpoints to access this information:

• GET /tcr/campaign/select — This endpoint returns an array of available TCR campaigns for your account.
• The response includes objects containing a campaignId field, which corresponds to the tcr_cid you will use when sending messages.
• Each campaign object also contains a proxy array. This array lists all phone numbers and area codes registered under that campaign.
• To select a specific area code or phone number for sending out a project, pass one of these phone numbers as the value of the tcr_phone field in your API request.
• The system will then route your message through the selected phone number's area code, allowing targeted sending based on your preferences.

Use "All" to select all proxy numbers from TCR campaign.

Short Urls

Q: How do I shorten URLs via the API?

A: To automatically shorten URLs in your message, include the shorturl_domain parameter in your POST /api/action/create request. This will automatically detect and shorten any URLs in the message body using the assigned short domain.

Q: Where can I find my available short URL domains?

A: Your available shorturl_domain options are managed by RumbleUp and tied to your organization. You can view them at the GET /uc/pub/settings endpoint.

Q: How do I include UTM tracking in a link inside the message text?

A: To include UTM tracking, construct your URL with UTM parameters and use placeholders to insert contact-specific or campaign-specific values. For example:
https://yoursite.com?utm_source=sms&utm_campaign=@custom1@&utm_medium=rumbleup\

Here, @custom1@ is a placeholder that will be replaced with a contact- or campaign-specific value when the message is sent. This allows you to personalize UTM parameters for detailed tracking in your analytics tools.

This approach also works with shortened URLs when using the shorturl_domain parameter. The placeholders embedded in the original URL are preserved and dynamically mapped when the recipient clicks the short link, ensuring personalized tracking even through the shortened link.

Outsourced Projects

Q: When do API projects require using RumbleUp’s outsourced sending teams?

A: If you don’t have your own sending team set up or haven’t integrated with our full Messaging API, projects created via the API need to use our outsourced sending teams. This way, you don’t have to manage sending yourself or log into the portal. Note that outsourced projects usually need to meet a minimum contact count to be eligible.