Clearing Segment Codes | Community
Skip to main content
derelict_wombat
derelict_wombat
Level 5
Oct 31, 2017 2:03 PM UTC
Solved

Clearing Segment Codes

I am a user of Campaign "classic" v. 6.11  and am trying to test a nurturing campaign where I am using segment codes to make sure that recipients who are part of one track do not get included in another track until the completion of the track.   I need to run some tests in order to see if the campaign workflows work as expected and wanted to know if there was a way to clear a segment code for a recipient after they complete the workflow and the code has been attributed to them.  Is there a place where segment codes are managed?

Thanks!   

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
christophec3473
christophec3473Accepted solution
Level 2
Dec 15, 2017 3:28 PM UTC

Hi,

You can get the temporary table name with a Javascript activity : vars.tableName.

After with a SQL activity, you can update a codeSegment of this temporary table.

Christophe

View reply

3 replies

christophec3473
christophec3473Accepted solution
Level 2
Dec 15, 2017 3:28 PM UTC

Hi,

You can get the temporary table name with a Javascript activity : vars.tableName.

After with a SQL activity, you can update a codeSegment of this temporary table.

Christophe

Translate
    florentlb
    florentlb
    Level 10
    Dec 4, 2017 3:36 PM UTC

    Hello,

    Any update on this topic? Let me know if I can help further.

    Florent

    Translate
    florentlb
    florentlb
    Level 10
    Nov 13, 2017 8:54 AM UTC

    Hi Matthew,

    If you are adding the segment code in the workflow, then it is only stored in a temporary table used by the workflow. If running the workflow again or running another workflow, the recipient should have no segment code attached.

    Please share more details and screenshots about your use case in case you are not doing it as I suggested.

    Let me know,

    Florent

    Translate
    Terms & ConditionsAccessibility statement

    Loading footer...