multiple Request Campaign API calls result in the same campaignRunId (?) | Community
Skip to main content
M
Mark_Price
Level 6
December 5, 2018
Question

multiple Request Campaign API calls result in the same campaignRunId (?)

  • December 5, 2018
  • 1 reply
  • 2691 views

Wondering if anyone has run into this issue system behavior.

We have a few recurring campaigns (weekly, monthly) that are triggered from a Request Campaign API call w/replacement tokens. If someone is sent the email 2 times, it looks like the campaignRunId is the same. Looking further into it, it looks like all the API call based sends for a campaign will have the same campaignRunId.

This is giving me headache because I was planning on using campaignRunId with some other data points as a unique identifier for the send. It seems like the API sends would need to fallback on a date/time logic in these cases.

Anyone else run into this?

Some campaigns have been converted to work off a field update and that seems to generate unique campaignRunIds so if there's no fix for Request Campaign, will have to go that route.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
December 5, 2018

Do you see the same if you chain the API-based ​Request Campaign ​to a second Flow-based ​Request Campaign​? ​(Leaving aside that the temporary tokens will be lost for the moment.)

    M
    Mark_PriceAuthor
    Level 6
    December 5, 2018

    Ran the tests on 2 records, results are below.  Results are not what I was expecting- the Flow Step Request Campaign has a similar system behavior of re-issuing the campaignRunId after it's generated.

    API-based Request Campaign Call #1: This is the first person in the campaign, so it created a campaignRunId

    Flow Step-based Request Campaign #1: Incremented by 1, generated another campaignRunId

    API-based Request Campaign Call #2: re-used campaignRunId from 1st API call

    Flow Step-based Request Campaign #2: re-used campaignRunId from previous Request Campaign flow step

    API-based Request Campaign Call #3: Using a different test lead, re-issued original API-based campaignRunId

    Flow Step-based Request Campaign #3 Using a different test lead, re-issued flow step campaignRunId

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    December 5, 2018

    Nice work as usual!

    Hit me up via email and we can try some other things.

      Terms & ConditionsAccessibility statement

      Loading footer...