Registry Valet Support: (919) 477-2100 (press option 1 for support)
support@agenne.com
Page: 1   2   3   4
Registry Valet FAQ
Settings Reference

Post Back to Registry Valet
Once the customer has made a purchase from a gift registry or wish list, you may optionally update the gift registry or wish list using the "Post Back" feature. There are two methods for accomplishing this:

  1. Using Cookies
  2. Fully Integrating Registry Valet with your cart system

One is easier and faster, the other is better. Let's start with the easy/fast version.

Integration using Cookies
When a customer makes a purchase from a gift registry, the item purchased is saved in a cookie which the customer is proceeding through checkout. Once they reach the final "receipt page", the item information is retrieved from the cookie and posted back to Registry Valet to update the registry. This method, although very simple to implement has two drawbacks. First, if the customer decides to change the quantity of the item(s) that they are buying, the cookie will have no way of knowing. The solution to this is to read the alert email that Registry Valet will send you and compare it to the order that the customer placed. The second drawback is that if the customer has disabled cookies in their browser (which is somewhat rare), then there will be no data passed to the receipt page.

To setup cookie-based integration, click Registry Settings in the administrator and change the "Integration Method" setting to "Cookie Based". Then, copy the following line of code and paste it into your shopping cart's receipt page:

<iframe src="https://apps.customcart.com/RegistryPostBackAction.cfm" height="0" width="0" frameborder="0"></iframe>

Note: If you are using a custom sub-domain (such as registry.mysite.com) instead of the default apps.agenne.com, you will need to substitute your custom sub-domain for apps.agenne.com in the line of code above. Using our example (registry.mysite.com), the correct line of code would be:

<iframe src="http://registry.mysite.com/RegistryPostBackAction.cfm" height="0" width="0" frameborder="0"></iframe>

That's all there is to it.

Full Integration
This option requires a little bit of technical expertise and your cart software must support the following:

  1. Registry Valet automatically includes additional form fields in the "Add to Cart" forms on the gift registry display page (where a customer views the list of desired items on a gift registry or wish list). These additional fields are a unique ID for the registered item and the name of the registrant. In order to complete the post back, your cart system must be capable of accepting these additional form fields and passing them on to the final receipt page in the checkout process.
  2. Your cart software must allow you to add a hidden form post to the final receipt page. This means that you will need access to the source code for your cart system. If you do not have access to the source code for your cart system, contact the manufacturer and ask them to contact us, we will be happy to assist them with integrating Registry Valet software into their cart software free of charge.

It is also important to note that in order for Registry Valet to pass the identifying variables to your cart software, you must use forms for your add-to-cart code and not links. Registry Valet can add additional fields to forms, but not to links.



An Overview of the Post Back Process
When the checkout process in your cart system is complete and reaches the final receipt page, the following takes place:
  1. You execute a hidden form post. There are a number of ways this can be accomplished, but the easiest is to create a hidden iframe, load an html page containing your form, and execute it when the receipt page loads using javascript.
  2. When Registry Valet receives your posted form data, it updates the posted records and responds with an XML document containing result codes for each item which you posted back information. For each gift item that you posted back to Registry Valet, there will be either a success or failure code which you may then use to alert the customer or retain for your own information. This XML document can optionally be disabled.


Post Back Form Example
Here is an example of the form you will use to post your gift item purchase data back to the gift registry:

<form action="https://apps.customcart.com/RegistryMultiPost.cfm" method="post">
<input type="hidden" name="CID" value="000">
<input type="hidden" name="count" value="5">
<input type="hidden" name="L_RVID" value="18082,20835,43012,15392,99999">
<input type="hidden" name="L_QTY" value="1,3,1,1,5">
</form>

Note that in the form above, five individual line items have been purchased and are being posted back to the gift registry. For each of these 5 items, the rvl_id (which was passed to your cart by the gift registry software when the shopper clicked "Add to Cart") is being posted back in the "L_RVID" field and the corresponding purchased quantities are being posted back in the "L_QTY" field.

Suppressing the XML response document using the optional suppressXML hidden field
By including the suppressXML field with a value of 1, in the form above, the XML document will not be returned. Instead, a page containing a single white pixel will be returned.

Here is how the suppressXML hidden form field should be included in the postback form:

<input type="hidden" name="suppressXML" value="1">



Sample XML Response
Here is an example of the XML document with which our software will respond when it receives posted data. Note that there is an rv_lineitem record for each gift item that you posted back to Registry Valet. In each case, a response code is returned, either "Success" or "Error". The XML response document is a simple way to help you debug your code.

<rv_result>

<rv_lineitem>
   <rec_id>18082</rec_id>
   <result>Success</result>
</rv_lineitem>

<rv_lineitem>
   <rec_id>20835</rec_id>
   <result>Success</result>
</rv_lineitem>

<rv_lineitem>
   <rec_id>43012</rec_id>
   <result>Error</result>
</rv_lineitem>

<rv_lineitem>
   <rec_id>15392</rec_id>
   <result>Success</result>
</rv_lineitem>

<rv_lineitem>
   <rec_id>99999</rec_id>
   <result>Error</result>
</rv_lineitem>

</rv_result>>

    Privacy Policy    |     Terms of Use    |