Submit a request

Custom Merge Codes And How To Use Them

Follow

Comments

7 comments

  • Avatar
    Jeremy Roberts

    This is an amazingly powerful feature -- for example, let's say you have slightly different layouts for some products. Instead of loading up each layout with the needed html, make a few custom mergecodes. This simplifies each layout's code and if you need to make an edit to the mergecode, only edit the source mergecode, not each layout.

    Why not use mergcodes with hidden widgets? Because they don't jump cross-layout.

    This is an extremely powerful function!!!

  • Avatar
    Marvin Hankins

    Apparently works in email templates too.

  • Avatar
    Brandon Young

    The only thing that would make these better would be the ability to provide arguments to the custom merge codes.

  • Avatar
    Austin Smith

    Brandon,

    I'm not 100% sure what you mean by argument -- Could you elaborate on that? Sounds interesting.

    --Austin
    SPOS Support

  • Avatar
    Brandon Young

    Austin,

    An argument similar to passing an argument to a function. For example, how you can pass arguments to the ##GOOGLECHECKOUT[size=small,bg=white,variant=text]## merge code.

  • Avatar
    Austin Smith

    Brandon,

    We do have some merge codes that accept arguments such as that; however, the google checkout merge code does not. It sounds like a great idea. I recommend suggesting it as a feature enhancement at vote.sparkpay.com.

    Cheers,
    Austin

  • Avatar
    Austin Smith

    Brandon,

    It is still valid! I was confusing it with `##GOOGLECONVERSIONTRACKINGASYNC##` which does not take arguments, as far as I'm aware.

    -Austin

Please sign in to leave a comment.