Skip to content

Anonymous

My feedback

1 result found

  1. 43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Feedback » Improvements  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    ISSUE: Currently a trigger is only url fired when a the url is exactly as provided by the admin, but should fire if unknown parameters are appended.

    SCENARIO CASE: When a user comes to the trigger url page from say an advertisement on google, the landing page, or trigger url, is appended with tracking and conversion parameters causing the trigger to never be fired.

    IMPROVEMENT IDEA OPTIONS:

    1. Provide option (checkbox) to filter url params out if they exist from URL.

    2. Filter out params entirely as if they do not exist

    3. Allow wildcard /* in the url to accept any params as they fall under the already provided trigger URL.

    ANYONE ELSE HAVE options or suggestion that can help get their dev team to iterate on this option in an upcoming sprint or deployment?

Feedback and Knowledge Base